Chapter 2 ADMIN


Severity	SEVERE/WARNING
Description	MBeanServer initialization failed. If this error message occurs in an admin instance, it has a SEVERE level, otherwise it is a WARNING message. This error occurs when the system mbeans could not be registered during system start-up and as a result the server does not start.
Action	Analyze the System, as described on (more...) .

ADM0006


Severity	WARNING
Description	Timestamp files could not be created. This error message occurs when Write access permission is not granted to the directory.
Action	See the detailed message that follows this error message. It may provide details of what occurred when the time-stamp files were created. Make sure you have Write access permission to the directory. If not, grant Write access permission to the config directory located in, (<install-dir>/domains/<domain-name>/<server-name>/config) and the backup directory located in, (<install-dir>/domains/<domain-name>/<server-name>/config/backup).

ADM0008


Severity	WARNING
Description	The Admin Server could not create the temporary folder for internal purposes in the temporary directory location. This may cause problems during deployment.
Action	Grant appropriate file permissions to enable writing to the file. Make sure that there is sufficient space for writing to the file in the temporary directory location.

ADM0011


Severity	WARNING
Description	Unable to re-register HttpListener with DomainRegistry. During the admin server instance startup, http-listeners associated with the server are registered in the domain registry. The domain registry is used to keep the domain-specific information, so that the admin server can be contacted by other domain’s admin servers. This error can occur if the domain registry is missing, that is the domains.bin file is missing from <Install_root/config> location.
Action	Restart the server.

ADM0014


Severity	WARNING
Description	The temporary folder required by the Administrator interface could not be created in the specified location. This poses 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.
Action	Free some space at the specified location so that the file can be created at this location, without restarting the admin server. Make sure that the directory has Write access permissions.

ADM0101


Severity	WARNING
Description	An error occurred while getting manual changes. This message occurs when there is a problem in the thread that tracks the manual changes performed in the configuration file, server.xml.
Action	Analyze the System, as described on (more...) .

ADM1002


Severity	WARNING
Description	Create instance failed. This error message occurs when the user is trying to create an instance, and the instance creation fails. See the accompanying detailed message to determine the actual reason for this failure. Two reasons may be: No space to create the instance. No permission to create the files in the designated directory.
Action	The detailed message in the log file helps determine the action to be taken.

ADM1004


Severity	WARNING
Description	Delete instance failed. This error message is reported when the deletion of a server instance fails to execute properly. The above message is followed by detailed error message that can help determine the actual reason for this failure.
Action	The detailed message in the log file helps determine the action to be taken.

ADM1008


Severity	WARNING
Description	Upload failed for the file at the specified location. This error message occurs when the output stream could not be closed when the server upload for deployment throws some exception.
Action	Analyze the System, as described on (more...) .

ADM1022


Severity	SEVERE
Description	The deployment procedure failed.
Action	See the exception stack trace for information on why the deployment failed.

ADM1024


Severity	SEVERE
Description	The undeployment procedure failed.
Action	See the exception stack trace for information on why the undeployment failed.

ADM1025


Severity	SEVERE
Description	The redeployment procedure failed.
Action	See the exception stack trace for information on why the redeployment failed.

ADM1026


Severity	SEVERE
Description	Redeployment failed.
Action	See the exception stack trace for information on why the redeployment failed.

ADM1028


Severity	WARNING
Description	List operation failed. This error message occurs when the admin server is unable to get a list of deployed applications, web-modules, resources or connectors.
Action	See the exception stack trace for information on why the list operation failed and how to fix the error.

ADM1030


Severity	WARNING
Description	Resource creation failed. This error message is logged when the creation of any resource, for example, jdbc-resource, jndi-resource, java-mail-resource, fails during execution.
Action	See the exception stack trace for information on why the resource creation failed and how to fix the error.

ADM1032


Severity	WARNING
Description	Resource deletion failed. This error message is logged when the deletion of any resource, for example, jdbc-resource, jndi-resource, java-mail-resource, fails during execution.
Action	See the exception stack trace for information on why the resource deletion failed and how to fix the error.

ADM1034


Severity	WARNING
Description	Deletion of connection pool failed. This error message occurs when the deletion of the chosen JDBC connection pool fails.
Action	See the exception stack trace for information on why the operation failed and how to fix the error.

ADM1037


Severity	WARNING
Description	Lifecycle module creation failed. This error message occurs when the lifecycle module could not be created successfully.
Action	See the exception stack trace for information on why the operation failed and how to fix the error.

ADM1039


Severity	WARNING
Description	Lifecycle module deletion failed. This error message occurs when the deletion of lifecycle module does not succeed.
Action	See the exception stack trace for information on why the operation failed and how to fix the error.

ADM1044


Severity	SEVERE
Description	The specified event will not be applied. This was applied as part of a prior event.
Action	No action to be taken.

ADM1046


Severity	WARNING
Description	Notification failed. This error message occurs when the admin server fails to notify the instances that are running of any changes made in the configuration of the server.
Action	Restart the server. If the problem persists, Analyze the System, as described on (more...) .

ADM1047


Severity	WARNING
Description	Setting JVM debug options in configuration file failed. This error message occurs when the server starts up in debug mode and fails.
Action	Make sure the server starts up normally. Make sure this port is free and restart the server.

ADM1050


Severity	SEVERE
Description	The specified starting instance failed. See instance logs for more details.
Action	See the ADM1069 message and instance level log file. The exact nature of failure can be determined and appropriate action can be taken.

ADM1059


Severity	WARNING
Description	Security check failed. This error message occurs when the authentication check fails during server instance startup.
Action	Make sure the init.conf file exists in the config directory. If the file exists, make sure the security value is correct.

ADM1060


Severity	WARNING
Description	isDebug check failed. This error message occurs while starting a server instance either in debug or normal mode. This means that the debug check for server start failed.
Action	Analyze the System, as described on (more...) .

ADM1069


Severity	WARNING
Description	The server instance startup failed. This error message occurs during server instance startup. See the detailed message to understand why the startup failed.
Action	Analyze the System, as described on (more...) .

ADM5002


Severity	WARNING
Description	Attempt to register a non-compliant monitoring mbean. This exception occurred while trying to register an Mbean in the MBean server that is not a JMX-compliant Mbean.
Action	Analyze the System, as described on (more...) .

ADM5003


Severity	WARNING
Description	MBean server initialization for monitoring failed. This error message occurs while trying to get the MBean server for registering or de-registering monitor mbeans.
Action	Analyze the System, as described on (more...) .

ADM5004


Severity	WARNING
Description	Monitoring channel initialization error occurred and hence monitoring is disabled. This error message occurs when the monitoring event listener is initialized. As a result of this, if a component has its monitoring enabled, it may be ignored, and the user may not be able to get the monitoring data. This error message should be read in conjunction with ADM5005 to determine the components that may not be monitored.
Action	Analyze the System, as described on (more...) .

ADM5005


Severity	WARNING
Description	Initialization of monitoring failed for the specified component. For a component to be monitored its monitoring enabled state should be initialized.
Action	Lookup components in the server.xml and ensure the specified component is not missing.

ADM5603


Severity	WARNING
Description	This is a generic error message that appears during deployment, or when configuration changes are made and also while monitoring the event handling process.
Action	Analyze the System, as described on (more...) .

ADM5609


Severity	SEVERE
Description	Unable to set the config context from the event multicast.
Action	Analyze the System, as described on (more...) .

ADM5801


Severity	WARNING
Description	This error occurs while creating communication channel between the admin server and the administered instance during server startup.
Action	Analyze the System, as described on (more...) .

ADM5802


Severity	WARNING
Description	This error occurs while creating communication channel between the admin server and the administered instance during server startup. The reason why this error occurred is due to an IO exception that occurred while reading one of the server system files.
Action	Analyze the System, as described on (more...) .

ADM5803


Severity	WARNING
Description	This error occurs while creating communication channel between the admin server and the administered instance during server startup. The cause for this is an IO exception while writing one of the server system files.
Action	Analyze the System, as described on (more...) .

ADM5804


Severity	WARNING
Description	This error occurs when the Admin server tries to check the client access and the address of client is null.
Action	Analyze the System, as described on (more...) .

ADM5805


Severity	WARNING
Description	Local access to admin server channel.
Action	Analyze the System, as described on (more...) .

ADM5807


Severity	WARNING
Description	Unable to determine the local host. This error occurs when the IP address of the local host where the server is running could not be determined.
Action	Make sure your machine has a valid IP address.

ADM5810


Severity	WARNING
Description	As part of establishing a communication link between the admin server and the administered instances, the admin channel client is created. If this creation fails, this error occurs.
Action	Analyze the System, as described on (more...) .

ADM5811


Severity	WARNING
Description	The admin channel auto refresh thread was interrupted.
Action	Analyze the System, as described on (more...) .

ADM5812


Severity	WARNING
Description	An event notification failed. This error occurs while sending an event notification over the admin channel from the admin server to the admin client. This event notification may be for deployment, monitoring, or config changes.
Action	Analyze the System, as described on (more...) .

ADM5813


Severity	WARNING
Description	If the event notification fails and the server stub file status is changed, a refresh operation is performed to get the stub file. It then retries for event notification and if it fails this error occurs.
Action	Analyze the System, as described on (more...) .

ADM5814


Severity	WARNING
Description	The stub file does not exist or cannot be read.
Action	Analyze the System, as described on (more...) .

ADM5815


Severity	WARNING
Description	An error occurred while initializing the admin channel client. An IO exception occurred while reading the stub from the stub file for the client in the admin channel.
Action	Analyze the System, as described on (more...) .

ADM6004


Severity	WARNING
Description	This error occurs when a command is sent to an Mbean from the Mbean server and the invocation fails.
Action	Analyze the System, as described on (more...) .

ADM6006


Severity	WARNING
Description	The Get attribute failed. An error occurred while getting the specified attribute of an Mbean from the MbeanServer.
Action	Analyze the System, as described on (more...) .

ADM6008


Severity	WARNING
Description	The Set attribute failed. An error occurred while setting the specified attribute of an Mbean from the Mbean server.
Action	Analyze the System, as described on (more...) .

ADM7003


Severity	WARNING
Description	JAVA_HOME value cannot be derived from the admin server's configuration file, and therefore an instance cannot be created.
Action	Make sure the JAVA_HOME is set in the admin server’s server.xml.

ADM7004


Severity	WARNING
Description	This error occurs when an instance is started, stopped or restarted through a subprocess and the subprocess gives an error or terminates abruptly.
Action	Analyze the System, as described on (more...) .

ADM7006


Severity	SEVERE
Description	The process of finding a free port on this system failed. The admin server tries to proceed by using default ports. See dtd/manuals for default port assignments.
Action	Contact the system administrator.

Previous Contents Index Next
Sun Java System Application Server 7 2004Q2 Update 1 Standard and Enterprise Edition Error Messages Reference