GlassFish v3 Error Message Reference
\

ADM

This page lists error messages with the ADM prefix.

See How to Contribute for more information about adding to and enhancing the information on this page.

----ADM0001 SunoneInterceptor is now enabled

Cause

TBD

Solution

TBD

----ADM0002 System MBean initialized:-(0)

Cause

TBD

Solution

TBD

----ADM0003 MBeanServer initialization failed

Cause

TBD

Solution

TBD

----ADM0004 MBeanServer method invocation:-(0)

Cause

TBD

Solution

TBD

----ADM0005 Timestamp files for configuration created for:-(0)

Cause

TBD

Solution

TBD

----ADM0006 Timestamp files not created - Detailed Message:

Cause

TBD

Solution

TBD

----ADM0007 The folder -(0) where admin server uploads the remote files for deployment already exists. This is probably because admin-server could not delete this folder during last shutdown. This should not be cause of any problem

Cause

TBD

Solution

TBD

----ADM0008 Admin Server could not create the temporary folder for internal purposes at -(0). This may cause problems with deployment etc. It is alright if some space is freed at this location without shutting down the Admin Server. Also look at the operating systems artifacts like file permissions etc. to resolve the problem

Cause

TBD

Solution

TBD

----ADM0009 Created temporary folder at -(0) for internal purpose

Cause

TBD

Solution

TBD

----ADM0010 Deleted temporary folder at -(0) successfully

Cause

TBD

Solution

TBD

----ADM0011 Could not re-register HttpListener with DomainRegistry.

Cause

TBD

Solution

TBD

----ADM0012 A Domain Registry Exception occurred. Details are:

Cause

TBD

Solution

TBD

----ADM0013 A config exception occurred. Details are:

Cause

TBD

Solution

TBD

----ADM0014 The temporary folder required by the administrative console (graphical user interface) could not be created at -(0). This will pose some problems while trying to deploy archives from the console. Some space can be freed at this location without restarting the administrative server to correct this problem.

Cause

TBD

Solution

TBD

----ADM0015 The temporary folder required by the administrative console (graphical user interface) was created at -(0). This is where the archives to be deployed will be uploaded.

Cause

TBD

Solution

TBD

----ADM0016 Unable to determine java home. This suggests that you are using a version of J2EE plug-in incompatible with administration server.

Cause

TBD

Solution

TBD

----ADM0017 Admin server could not be initialized with java home from j2ee plug-in.

Cause

TBD

Solution

TBD

----ADM0018 Support for batched reconfiguration is disabled.

Cause

TBD

Solution

TBD

----ADM0019 Admin service is running without server context.

Cause

TBD

Solution

TBD

----ADM0020 Following is the information about the JMX MBeanServer used:

Cause

TBD

Solution

TBD

----ADM0021 MBeanServer Implementation Name:-(0)

Cause

TBD

Solution

TBD

----ADM0022 MBeanServer Implementation Vendor:-(0)

Cause

TBD

Solution

TBD

----ADM0033 Admin Service configuration could not be read and Admin Service type is being defaulted to -(0)

Cause

TBD

Solution

TBD

----ADM0034 Preinvoke failed for MBeanServer interceptor -(0).

Cause

TBD

Solution

TBD

----ADM0035 Preinvoke exception for MBeanServer interceptor.

Cause

TBD

Solution

TBD

----ADM0036 Postinvoke failed for MBeanServer interceptor -(0).

Cause

TBD

Solution

TBD

----ADM0037 Preinvoke exception for MBeanServer interceptor.

Cause

TBD

Solution

TBD

----ADM0038 A read-write version of configuration files could not be loaded. Server can not be administered. Root cause: -(0)

Cause

TBD

Solution

TBD

----ADM0039 Read/Write version of configuration files not loaded because of exception.

Cause

TBD

Solution

TBD

----ADM0040 Config context for runtime initialized to -(0)

Cause

TBD

Solution

TBD

----ADM0041 Config context for admin initialized to -(0)

Cause

TBD

Solution

TBD

----ADM0042 Log Manager MBean could not be registered, the changes to logger log levels will be effective after server restart.

Cause

TBD

Solution

TBD

----ADM0043 Log Manager MBean registration aborted because of exception.

Cause

TBD

Solution

TBD

----ADM0044 Admin authentication using realm -(0) did not work.

Cause

TBD

Solution

TBD

----ADM0045 Error in admin authentication.

Cause

TBD

Solution

TBD

----ADM0046 Error during callflow agent creation.

Cause

TBD

Solution

TBD

----ADM0047 Error during initialization of mechanism to notify Node Agents associated with this Domain Administration Server

Cause

TBD

Solution

TBD

----ADM0048 Could not determine from the config context if the instance is a DAS instance

Cause

TBD

Solution

TBD

----ADM0049 System Services MBean -(0) could not be registered.

Cause

TBD

Solution

TBD

----ADM0050 Custom (user or system defined) MBeans could not be registered in MBeanServer. Check the configuration of these MBeans.

Cause

TBD

Solution

TBD

----ADM0101 Error getting manual changes

Cause

TBD

Solution

TBD

----ADM0102 Starting a thread for tracking manual changes

Cause

TBD

Solution

TBD

----ADM0103 Stopping the thread for tracking manual changes

Cause

TBD

Solution

TBD

----ADM023 JMX Implementation Version:-(0)

Cause

TBD

Solution

TBD

----ADM024 MBeanServer ID:-(0)

Cause

TBD

Solution

TBD

----ADM025 MBeanServer Implementation Classname:-(0)

Cause

TBD

Solution

TBD

----ADM026 Using HtmlAdaptorServer for viewing MBeans, its state is:-(0)

Cause

TBD

Solution

TBD

----ADM027 Using HtmlAdaptorServer for viewing MBeans, its port is: -(0). Connect the Browser to this port

Cause

TBD

Solution

TBD

----ADM028 The MBean with ObjectName-(0) was created anew and registered with the MBeanServer

Cause

TBD

Solution

TBD

----ADM029 The MBean with ObjectName-(0) already exists, accessing its management interface

Cause

TBD

Solution

TBD

----ADM030 The ObjectName -(0) can''t be registered as the configuration does not have it

Cause

TBD

Solution

TBD

----ADM031 Html Adaptor Server stopped

Cause

TBD

Solution

TBD

----ADM032 The System MBeanServer released

Cause

TBD

Solution

TBD

----ADM051 MBeans that provide additional JVM monitoring information like system memory could not be registered.

Cause

TBD

Solution

TBD

----ADM1001 New Server Instance -(0) created successfully

Cause

TBD

Solution

TBD

----ADM1002 Create Instance failed

Cause

TBD

Solution

TBD

----ADM1003 Deleted Server Instance -(0) successfully

Cause

TBD

Solution

TBD

----ADM1004 Delete Instance failed

Cause

TBD

Solution

TBD

----ADM1006 Uploading the file to:-(0)

Cause

TBD

Solution

TBD

----ADM1007 Uploaded the remote file at: -(0)

Cause

TBD

Solution

TBD

----ADM1008 Upload failed for file at: -(0)

Cause

TBD

Solution

TBD

----ADM1009 Can''t get MBeanInfo for: -(0)

Cause

TBD

Solution

TBD

----ADM1010 Preparing to download the file:-(0)

Cause

TBD

Solution

TBD

----ADM1011 Starting the download ...

Cause

TBD

Solution

TBD

----ADM1012 Downloading the file to client failed

Cause

TBD

Solution

TBD

----ADM1021 Deploying the archive:-(0)

Cause

TBD

Solution

TBD

----ADM1022 Deployment failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1023 Undeploying the deployed archive:-(0)

Cause

TBD

Solution

TBD

----ADM1024 Undeployment failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1025 Redeploying the deployed archive:-(0)

Cause

TBD

Solution

TBD

----ADM1026 Redeployment failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1027 Listing entities

Cause

TBD

Solution

TBD

----ADM1028 List operation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1029 Creating resource:-(0)

Cause

TBD

Solution

TBD

----ADM1030 Resource creation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1031 Deleting resource:-(0)

Cause

TBD

Solution

TBD

----ADM1032 Resource creation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1033 Deleting JDBC Connection Pool: -(0)

Cause

TBD

Solution

TBD

----ADM1034 Deletion of Connection Pool failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1036 Created lifecycle module:-(0)

Cause

TBD

Solution

TBD

----ADM1037 Lifecycle module creation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1038 Deleted lifecycle module:-(0)

Cause

TBD

Solution

TBD

----ADM1039 Lifecycle module deletion failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1040 Client-jar location:-(0)

Cause

TBD

Solution

TBD

----ADM1041 Sent the event to instance:-(0)

Cause

TBD

Solution

TBD

----ADM1042 Status of dynamic reconfiguration event processing:-(0)

Cause

TBD

Solution

TBD

----ADM1043 Response of instance on listening event:-(0)

Cause

TBD

Solution

TBD

----ADM1044 This event will not be applied:-(0). This is because it was applied as a part of a prior event.

Cause

TBD

Solution

TBD

----ADM1045 Sent the event:-(0)

Cause

TBD

Solution

TBD

----ADM1046 A change notification was not handled successfully. The server will need a restart for the change to be effective.

Cause

TBD

Solution

TBD

----ADM1047 Setting jvm debug options in configuration file failed

Cause

TBD

Solution

TBD

----ADM1048 Stopping the server instance:-(0)

Cause

TBD

Solution

TBD

----ADM1049 Starting the server instance:-(0)

Cause

TBD

Solution

TBD

----ADM1050 Starting instance -(0) failed. See instance logs for more details

Cause

TBD

Solution

TBD

----ADM1051 Debug options for the instance are set to:-(0)

Cause

TBD

Solution

TBD

----ADM1052 Beginning to check status of START instance:-(0)

Cause

TBD

Solution

TBD

----ADM1053 Beginning to check status of STOP instance:-(0)

Cause

TBD

Solution

TBD

----ADM1054 Checking of START instance timed out for: -(0)

Cause

TBD

Solution

TBD

----ADM1055 Checking of STOP instance timed out for: -(0)

Cause

TBD

Solution

TBD

----ADM1056 Successfully started instance: -(0)

Cause

TBD

Solution

TBD

----ADM1057 Successfully stopped instance: -(0)

Cause

TBD

Solution

TBD

----ADM1058 Restarting the server instance : -(0)

Cause

TBD

Solution

TBD

----ADM1059 Security check failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1060 isDebug check failed. Detailed Message:

Cause

TBD

Solution

TBD

----ADM1061 Skipping notifications because instance -(0) is not running.

Cause

TBD

Solution

TBD

----ADM1062 The temporary file uploaded at -(0) deleted. This does not necessarily imply that the deployment request from an administrative interface was served successfully

Cause

TBD

Solution

TBD

----ADM1063 The temporary file -(0) used to upload before deployment could not be deleted, most likely because the file handle is occupied by admin server runtime. If a file with the same name is to be deployed again, this file will be overwritten during upload, which should not be a problem in future deployments. Please try deleting this file, if you see this message.

Cause

TBD

Solution

TBD

----ADM1064 The upload file at -(0) exists and will be overwritten.

Cause

TBD

Solution

TBD

----ADM1065 Beginning to stop the domain -(0). The administrative server will also be shutdown along with all the other running non administrative SunONE Application Server instances

Cause

TBD

Solution

TBD

----ADM1066 Beginning to stop the domain -(0). The administrative server will not be shutdown. Only the non administrative SunONE Application Server instances will be shutdown

Cause

TBD

Solution

TBD

----ADM1067 Deletion of JMS service instance failed.

Cause

TBD

Solution

TBD

----ADM1068 Stopping instance -(0) failed. See instance logs for more details

Cause

TBD

Solution

TBD

----ADM1069 Starting the server instance failed. Detailed message:

Cause

TBD

Solution

TBD

----ADM1070 Starting the server instance:-(0) in debug mode with JPDA port number -(1)

Cause

TBD

Solution

TBD

----ADM1071 Ownership of deployment directories could not be changed. -(0)

Cause

TBD

Solution

TBD

----ADM1072 Size of the file -(0) could not be verified

Cause

TBD

Solution

TBD

----ADM1073 Error while trying to determine fully qualified name of this host.

Cause

TBD

Solution

TBD

----ADM1074 Could not determine fully qualified name of current host, will use localhost.

Cause

TBD

Solution

TBD

----ADM1075 Error on listening event:-(0)

Cause

TBD

Solution

TBD

----ADM1076 Could not determine port to form web service endpoint, will use default port -(0).

Cause

TBD

Solution

TBD

----ADM1077 IOException while accessing autostart file.

Cause

TBD

Solution

TBD

----ADM1078 Autostart could not be enabled. Access to file -(0) failed with error -(1).

Cause

TBD

Solution

TBD

----ADM1079 Initialization of AMX MBeans started

Cause

TBD

Solution

TBD

----ADM1080 Initialization of AMX MBeans failed. Detailed message:

Cause

TBD

Solution

TBD

----ADM1081 Creating the application reference -(0)

Cause

TBD

Solution

TBD

----ADM1082 Creating the application reference failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1083 Deleting the application reference -(0)

Cause

TBD

Solution

TBD

----ADM1084 Deleting the application reference failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1085 Starting the application -(0)

Cause

TBD

Solution

TBD

----ADM1086 Starting the application failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1087 Stopping the application -(0)

Cause

TBD

Solution

TBD

----ADM1088 Stopping the application failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM1089 A change notification was not handled successfully. Details about each server instance and its corresponding notification success status -(0).

Cause

TBD

Solution

TBD

----ADM1090 A change notification was not handled successfully. Details about each server instance and its corresponding notification exceptions and messages -(0).

Cause

TBD

Solution

TBD

----ADM11001 Error creating table {0} as table already exists

Cause

TBD

Solution

TBD

----ADM11002 Error creating table {0}. Most likely cause is that table already exists. Please look at the following exception.

Cause

TBD

Solution

TBD

----ADM11003 Error enabling callflow.

Cause

TBD

Solution

TBD

----ADM11004 Failed getting a connection to the callflow database

Cause

TBD

Solution

TBD

----ADM11005 Error executing query request information to the database.

Cause

TBD

Solution

TBD

----ADM11006 Error executing query callstack information to the database.

Cause

TBD

Solution

TBD

----ADM11007 Error executing query pie information to the database.

Cause

TBD

Solution

TBD

----ADM11008 ClearData disabled. Turn Call Flow off before calling clearData.

Cause

TBD

Solution

TBD

----ADM11009 CallFlow enable successful.

Cause

TBD

Solution

TBD

----ADM11010 CallFlow disable successful

Cause

TBD

Solution

TBD

----ADM11011 Call flow request start operation failed.

Cause

TBD

Solution

TBD

----ADM11012 Call flow add request info operation failed.

Cause

TBD

Solution

TBD

----ADM11013 Adding request information is disallowed after request initialization is completed. Request initialization is completed during the first startTime operation.

Cause

TBD

Solution

TBD

----ADM11014 Call flow request end operation failed.

Cause

TBD

Solution

TBD

----ADM11015 Call flow start time operation failed.

Cause

TBD

Solution

TBD

----ADM11016 Call flow end time operation failed.

Cause

TBD

Solution

TBD

----ADM11017 Call flow EJB method start operation failed.

Cause

TBD

Solution

TBD

----ADM11018 Call flow EJB method end operation failed.

Cause

TBD

Solution

TBD

----ADM11019 Call flow web method start operation failed.

Cause

TBD

Solution

TBD

----ADM11020 Call flow web method end operation failed.

Cause

TBD

Solution

TBD

----ADM11021 Call flow asynchronous writer thread interrupted.

Cause

TBD

Solution

TBD

----ADM11022 Database write operation by call flow asynchronous thread failed.

Cause

TBD

Solution

TBD

----ADM11023 Data transfer to call flow asynchronous thread interrupted.

Cause

TBD

Solution

TBD

----ADM1500 Initializing the lifecycle module for JMX Connector

Cause

TBD

Solution

TBD

----ADM1501 Here is the JMXServiceURL for the JMXConnectorServer: -(0). This is where the remote administrative clients should connect using the standard JMX Connectors.

Cause

TBD

Solution

TBD

----ADM1502 Status of System JMX Connector: Active = -(0)

Cause

TBD

Solution

TBD

----ADM1503 The system-jmx-connector port -(0) is not enabled to start with server startup. Thus JSR 160 JMX Connector will not be started.

Cause

TBD

Solution

TBD

----ADM1504 Here is the JMXServiceURL for the Standard JMXConnectorServer: -(0). This is where the remote administrative clients should connect using the standard JMX connectors

Cause

TBD

Solution

TBD

----ADM1506 Status of Standard JMX Connector: Active = -(0)

Cause

TBD

Solution

TBD

----ADM1509 JSR 160 JMX Connector Server at address -(0) is now stopping

Cause

TBD

Solution

TBD

----ADM1510 JSR 160 JMX Connector Server is now shutdown

Cause

TBD

Solution

TBD

----ADM1600 The MBean, {0}, was successfully deleted dynamically.

Cause

TBD

Solution

TBD

----ADM1601 Received a request for registration of MBean, {0}, but it is already registered in the MBeanServer.

Cause

Registration of the MBean was unsuccessful because it is already registered.

Solution

Run 'asadmin list-mbeans' to see a list of registered MBeans

----ADM1602 The MBean, {0}, was successfully registered in the MBeanServer.

Cause

TBD

Solution

TBD

----ADM1603 Unable to unregister the MBean, {0}. This MBean was never registered in the MBeanServer. In general, this should not be a problem.

Cause

Unregistration of the MBean failed because it is not registered.

Solution

Run 'asadmin list-mbeans' to see a list of registered MBeans

----ADM1604 The MBean, {0}, was successfully unregistered from the MBeanServer.

Cause

TBD

Solution

TBD

----ADM1605 Received a ConfigChange event for: -(0)

Cause

TBD

Solution

TBD

----ADM1606 Can''t handle updating an MBean element itself ({0}). The MBean is updated in terms of its xml-attributes, none of which are dynamically reconfigurable.

Cause

Can't handle updating an MBean element

Solution

Note that none of the attributes of "mbean" element except 'enabled' and 'object-name' are modifiable dynamically. Only the properties in this element that are actually the attributes of the runtime mbean are modifiable dynamically.

----ADM1607 Received an MBean change event, but the MBean, {0}, is disabled. Disabled MBeans can''t have their state changed.

Cause

Disabled MBeans are not allowed to have their state changed

Solution

Try enabling the MBean

----ADM1608 An MBean with name: {0} could not be loaded. Continuing to load other MBeans";

Cause

The MBeanServer refused to load the MBean

Solution

Try redeploying the MBean

----ADM1609 Attempting to load mbean: {0}

Cause

TBD

Solution

TBD

----ADM1610 The real mbean object-name would be: {0}

Cause

TBD

Solution

TBD

----ADM1611 The Class: {0} could not be loaded by class loader: {1} or any of its parents.

Cause

TBD

Solution

TBD

----ADM1612 The Class: {0} could not be initialized by class loader: {1} or any of its parents.

Cause

TBD

Solution

TBD

----ADM1613 The Class: {0} could not be instantiated because it appears to be an interface or abstract class. Check MBean code.

Cause

TBD

Solution

TBD

----ADM1614 The Class: {0} could not be could not be instantiated because of illegal access or default constructor not being available. Check MBean code.

Cause

TBD

Solution

TBD

----ADM1615 The Class: {0} could not be instantiated because of an error in static initializer. Check MBean code.

Cause

TBD

Solution

TBD

----ADM1616 MBean Class: {0} initiating class loader: {1}, defining class loader: {2}

Cause

TBD

Solution

TBD

----ADM1617 Setting attribute: {0} on mbean: {1}

Cause

TBD

Solution

TBD

----ADM1618 Can''t unregister MBean: {0}

Cause

Can not unregister the MBean. This is a non-fatal error.

Solution

Try restarting the AppServer

----ADM1619 handleUpdate ..... Remote Server: received – {0} {1}

Cause

TBD

Solution

TBD

----ADM1620 handleDelete ..... Remote Server: received – {0} {1}

Cause

TBD

Solution

TBD

----ADM1621 handleCreate ..... Remote Server: received – {0} {1}

Cause

TBD

Solution

TBD

----ADM1622 The parent directory was created successfully: {0}

Cause

TBD

Solution

TBD

----ADM1623 The parent directory could not be created: {0}

Cause

TBD

Solution

TBD

----ADM1624 The MBean class file was downloaded here: {0}

Cause

TBD

Solution

TBD

----ADM1625 The Standard MBean interface file was downloaded from: {0}

Cause

TBD

Solution

TBD

----ADM1626 This is not a standard MBean, because the corresponding standard MBean interface could not be found

Cause

TBD

Solution

TBD

----ADM1627 Instance Root for DAS: {0}

Cause

TBD

Solution

TBD

----ADM1628 DAS MBeans are stored at this DAS location: {0}

Cause

TBD

Solution

TBD

----ADM1629 MBean just created is at this DAS location: {0}

Cause

TBD

Solution

TBD

----ADM1630 MBean will be copied here: {0}

Cause

TBD

Solution

TBD

----ADM1631 The MBean Definition: {0} already exists in the domain

Cause

TBD

Solution

TBD

----ADM1632 The ObjectName: {0} already exists in target: {1}

Cause

TBD

Solution

TBD

----ADM1633 The attribute -(0) doesn''t exist in the MBean. Here is a list of accessible attributes: {1}

Cause

TBD

Solution

TBD

----ADM1634 The attribute -(0) is a character attribute. You can set it with a String of length=1 only. You tried to set it to -(1)

Cause

TBD

Solution

TBD

----ADM2001 Attribute -(0) is not found

Cause

TBD

Solution

TBD

----ADM2002 Can not get MBean Info.

Cause

TBD

Solution

TBD

----ADM2003 GenericConfigurator: getting attribute for dotted name: -(0)

Cause

TBD

Solution

TBD

----ADM2004 GenericConfigurator: setting attribute for dotted name: -(0)=-(1)

Cause

TBD

Solution

TBD

----ADM2005 ConfigMBeanBase:getting value for attribute -(0)

Cause

TBD

Solution

TBD

----ADM2006 ConfigMBeanBase:set attribute -(0)=-(1)

Cause

TBD

Solution

TBD

----ADM2007 ConfigMbeanBase:Returned value for attribute -(0) is -(1)(string)/-(2)(after conversion)

Cause

TBD

Solution

TBD

----ADM2008 ConfigMBeanBase: getting property -(0)

Cause

TBD

Solution

TBD

----ADM2009 ConfigMBeanBase: setting property -(0)=-(1)

Cause

TBD

Solution

TBD

----ADM2010 ConfigMBeanBase:getting default value for attribute -(0)

Cause

TBD

Solution

TBD

----ADM2011 Apply Changes failed for admin instance. Root cause: -(0)

Cause

TBD

Solution

TBD

----ADM2012 Check to determine whether changes can be applied failed, assuming can not apply changes. Root cause: -(0)

Cause

TBD

Solution

TBD

----ADM2013 Unable to use manual changes to configuration. Root Cause: -(0)

Cause

TBD

Solution

TBD

----ADM2014 Unable to determine whether admin instance configuration has been changed and not applied. Root cause: -(0)

Cause

TBD

Solution

TBD

----ADM2015 Get config bean by xpath: -(0)

Cause

TBD

Solution

TBD

----ADM2016 Get list continuations for dotted name: -(0)

Cause

TBD

Solution

TBD

----ADM2017 Malformed dotted name: -(0)

Cause

TBD

Solution

TBD

----ADM2018 Exception during List names continuation operation. Detailed message:

Cause

TBD

Solution

TBD

----ADM2019 Getting default values for instance: {0}; MBean Type: {1}

Cause

TBD

Solution

TBD

----ADM2020 Error initializing dotted Names

Cause

TBD

Solution

TBD

----ADM2021 MBean class -(0) using is config id -(1)

Cause

TBD

Solution

TBD

----ADM3000 Exception listing password aliases

Cause

TBD

Solution

TBD

----ADM5001 Root Monitoring MBean -(0) registered successfully

Cause

TBD

Solution

TBD

----ADM5002 Attempt to register non-compliant monitoring mbean -(0)

Cause

TBD

Solution

TBD

----ADM5003 MBean Server initialization for monitoring failed.

Cause

TBD

Solution

TBD

----ADM5004 Monitoring channel initialization error. Monitoring will be disabled.

Cause

TBD

Solution

TBD

----ADM5005 Initialization of monitoring failed for component -(0)

Cause

TBD

Solution

TBD

----ADM5006 Monitoring MBean for component -(0) could not be purged.

Cause

TBD

Solution

TBD

----ADM5007 Monitoring MBean could not be purged.

Cause

TBD

Solution

TBD

----ADM5008 User ORB monitoring component name -(0) is in use.

Cause

TBD

Solution

TBD

----ADM5009 ORB monitoring mbean named -(0) registered

Cause

TBD

Solution

TBD

----ADM5010 Invalid hint -(0) for user ORB monitoring component name will be ignored.

Cause

TBD

Solution

TBD

----ADM5601 Multicast event from instance -(0) to -(1) not supported.

Cause

TBD

Solution

TBD

----ADM5602 Event handler initialization error -(0)

Cause

TBD

Solution

TBD

----ADM5603 Event listener error -(0)

Cause

TBD

Solution

TBD

----ADM5604 Processing config change -(0)

Cause

TBD

Solution

TBD

----ADM5605 Config Change or its xpath is null! Ignoring -(0)

Cause

TBD

Solution

TBD

----ADM5606 Extracting changes to -(0)

Cause

TBD

Solution

TBD

----ADM5607 Config change xpath is -(0)

Cause

TBD

Solution

TBD

----ADM5608 Purging NO-OP event -(0)

Cause

TBD

Solution

TBD

----ADM5609 Unknown server context type -(0). Unable to set the config context from the event multicaster.

Cause

Event subsystem does not recognize the new implementation of the server context found in runtime.

----ADM5610 List of updated attributes is null for xpath -(0).

Cause

TBD

Solution

TBD

----ADM5611 Attempt to extract token number -(1) from -(0) when it contains only -(2) tokens.

Cause

TBD

Solution

TBD

----ADM5612 Attempt to replace config context in ConfigFactory Failed.

Cause

TBD

Solution

TBD

----ADM5613 The key type of the following class, is not allowed in admin event: -(0)

Cause

TBD

Solution

TBD

----ADM5614 The object key in the current event is malformed : -(0)

Cause

TBD

Solution

TBD

----ADM5615 The following object name is malformed: -(0)

Cause

TBD

Solution

TBD

----ADM5616 Admin channel did not return RMI client. Could not reset restart required.

Cause

TBD

Solution

TBD

----ADM5617 Unexpected error during resetting of restart required flag.

Cause

TBD

Solution

TBD

----ADM5618 Restart required status is not updated correctly for the following configuration change (XPath is -(0)).

Cause

TBD

Solution

TBD

----ADM5619 Target -(0) could not be resolved. Invalid Name.

Cause

TBD

Solution

TBD

----ADM5620 Target -(0) does not contain any servers. Restart required is not set for this target.

Cause

TBD

Solution

TBD

----ADM5621 Delete of prior config element failed.

Cause

TBD

Solution

TBD

----ADM5622 Update for the ConfigAdd event failed.

Cause

TBD

Solution

TBD

----ADM5623 Attribute {0} not found in the MBean Registry.

Cause

TBD

Solution

TBD

----ADM5801 Admin server channel creation failed.

Cause

TBD

Solution

TBD

----ADM5802 Error reading key file.

Cause

TBD

Solution

TBD

----ADM5803 Error writing key file.

Cause

TBD

Solution

TBD

----ADM5804 Client host is null.

Cause

TBD

Solution

TBD

----ADM5805 Local access to admin server channel.

Cause

TBD

Solution

TBD

----ADM5806 Address mismatch: client/-(0) server/-(1)

Cause

TBD

Solution

TBD

----ADM5807 Unable to determine local host.

Cause

TBD

Solution

TBD

----ADM5808 Shared key mismatch: client/-(0) server/-(1)

Cause

TBD

Solution

TBD

----ADM5809 Error sending reconfig signal.

Cause

TBD

Solution

TBD

----ADM5810 Attempt to initialize admin channel client with null arguments.

Cause

TBD

Solution

TBD

----ADM5811 Admin channel auto refresh thread interrupted.

Cause

TBD

Solution

TBD

----ADM5812 Event notification fialed.

Cause

TBD

Solution

TBD

----ADM5813 Event notification retry failed.

Cause

TBD

Solution

TBD

----ADM5814 File -(0) does not exist or can not be read.

Cause

TBD

Solution

TBD

----ADM5815 Error initializing admin channel client.

Cause

TBD

Solution

TBD

----ADM5816 Communication error over admin channel -(0).

Cause

TBD

Solution

TBD

----ADM5817 Dynamic Reconfiguration module for web tier could not be enabled.

Cause

TBD

Solution

TBD

----ADM5818 Shared key file (last modified -(0)) is older than channel file (last modified -(1)).

Cause

TBD

Solution

TBD

----ADM6001 Remote client communication started

Cause

TBD

Solution

TBD

----ADM6002 Received remote administration request

Cause

TBD

Solution

TBD

----ADM6003 Invoked the mbean:-(0)

Cause

TBD

Solution

TBD

----ADM6004 Remote invocation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM6005 Got attributes from the mbean:-(0)

Cause

TBD

Solution

TBD

----ADM6006 Get attributes failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM6007 Set attributes in the mbean:-(0)

Cause

TBD

Solution

TBD

----ADM6008 Set attributes failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM7001 Name of the attribute:-(0)

Cause

TBD

Solution

TBD

----ADM7002 Name of the instance:-(0)

Cause

TBD

Solution

TBD

----ADM7003 Instance creation failed - Detailed Message:

Cause

TBD

Solution

TBD

----ADM7004 Executing the command in a subprocess:-(0)

Cause

TBD

Solution

TBD

----ADM7005 Stopping the Server Instance failed. Deleting the configuration folder, please kill the processes

Cause

TBD

Solution

TBD

----ADM7006 Process of finding out free port on this system failed. Generally not being able to find a free port indicates a current or potential problem. Administration server will try to proceed by using default ports. See dtd/manuals for default port assignments

Cause

TBD

Solution

TBD

----ADM7007 Permanent certs in certdb:-(0)

Cause

TBD

Solution

TBD

----ADM7008 CA certs in certdb:-(0)

Cause

TBD

Solution

TBD

----ADM7009 Cert nickname:-(0)

Cause

TBD

Solution

TBD

----ADM7010 Unexpected exception or error.

Cause

TBD

Solution

TBD

----ADM7011 Although instance {0} was removed, it was not deleted completely. Some files or directories may have been in use at the time. Please manually delete the instance directory to ensure complete deletion.

Cause

TBD

Solution

TBD

----ADM8001 Failed to publish Web Service {0} to registries.

Cause

TBD

Solution

TBD

----ADM8002 Failed to publish Web Service to registries.

Cause

TBD

Solution

TBD

----ADM8003 Web Service {0} published successfully to registries.

Cause

TBD

Solution

TBD

----ADM8004 Failed to unpublish Web Service {0} from registries.

Cause

TBD

Solution

TBD

----ADM8005 Failed to unpublish Web Service from registries.

Cause

TBD

Solution

TBD

----ADM8006 Unpublished Web Service {0} from registries.

Cause

TBD

Solution

TBD

----ADM8007 Cannot find a connector module of type {0}. Deploy a connector module with type {0}

Cause

TBD

Solution

TBD

----ADM8008 Registry type unspecified. Registry type has to be either {0} or {1}.

Cause

TBD

Solution

TBD

----ADM8009 Cannot add Registry Location to Web Service End point in domain.xml

Cause

TBD

Solution

TBD

----ADM8010 Invalid Web Service Name {0}. Cannot publish Web Service to registries.

Cause

TBD

Solution

TBD

----ADM8011 WSDL not found for Web Service {0}. Cannot publish Web Service to registries.

Cause

TBD

Solution

TBD

----ADM8012 Registry Location {0} not found. Cannot publish Web Service to it.

Cause

TBD

Solution

TBD

----ADM8013 Registry Location not found. Cannot publish Web Service to it.

Cause

TBD

Solution

TBD

----ADM8014 Web Service {0} not published. Look at preceding errors for probable causes.

Cause

TBD

Solution

TBD

----ADM8015 Invalid Web Service Name {0}. Cannot publish Web Service from registries.

Cause

TBD

Solution

TBD

----ADM8016 Registry Location {0} not found. Cannot unpublish Web Service from it.

Cause

TBD

Solution

TBD

----ADM8017 Registry Location not found. Cannot unpublish Web Service to it.

Cause

TBD

Solution

TBD

----ADM8018 Web Service {0} not unpublished. Look at preceding errors for probable causes.

Cause

TBD

Solution

TBD

----ADM8019 Cannot list registry location.

Cause

TBD

Solution

TBD

----ADM8020 WSDL not found for Web Service {0}.

Cause

TBD

Solution

TBD

----ADM8021 Access URI for Web Serivce {0} is {1}.

Cause

TBD

Solution

TBD

----ADM8022 Cannot create Service Object in the registry.

Cause

TBD

Solution

TBD

----ADM8023 Cannot create Service Binding Object in the registry.

Cause

TBD

Solution

TBD

----ADM8024 Failed to create Slots to categorize categories in the registry.

Cause

TBD

Solution

TBD

----ADM8025 Failed to create Classification and ClassificationScheme Object in the registry/

Cause

TBD

Solution

TBD

----ADM8026 Organization {0} successfully published to registry.

Cause

TBD

Solution

TBD

----ADM8027 Organization {0} could not be published to registry. Look at the following exceptions for probable causes.

Cause

TBD

Solution

TBD

----ADM8028 Cannot find Classification Scheme for Web Service {0}. Cannot unpublish from registry. Please unpublish manually.

Cause

TBD

Solution

TBD

----ADM8029 Issuing request to unpublish {0} from Organization {1}.

Cause

TBD

Solution

TBD

----ADM8030 Failed to unpublish Web Service from Registry.

Cause

TBD

Solution

TBD

----ADM8031 Failed to delete Classification Scheme Object {0} from the registry. Please delete manually.

Cause

TBD

Solution

TBD

----ADM8032 Deleted Classification Scheme Object {0} successfully for Web Service {1}.

Cause

TBD

Solution

TBD

----ADM8033 Organization {0} has services - cannot delete it. Please delete all services from registry first.

Cause

TBD

Solution

TBD

----ADM8044 Delete Organization {0} operation failed. Please delete it manually from the registry.

Cause

TBD

Solution

TBD

----ADM8045 Delete Services {0} operation failed. Please delete it manually from registry.

Cause

TBD

Solution

TBD

----ADM8046 Delete ServiceBinding {0} operation failed. Delete it manually from registry.

Cause

TBD

Solution

TBD