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

> ## Chapter 5
> Core Services

> This chapter lists error messages that originate from the Core services.

> ##

> CORE

> ##### CORE3283

> Severity | ERROR
> Description | An IOException occurred.
> Action | This error has been seen when trying to connect to HADB.

> ##### CORE4001

> Severity | WARNING
> Description | An error occurred when a request processing thread tried to connect to the Java Virtual Machine.
> Action | Restart the server. If the problem persists, Analyze the System, as described on (more...) .

> ##### CORE4002

> Severity | WARNING
> Description | An error occurred when a request processing thread tried to disconnect from the Java Virtual Machine.
> Action | Restart the server. If the problem persists, Analyze the System, as described on (more...) .

> ##### CORE4003

> Severity | WARNING
> Description | No name has been specified for the <profiler> element in server.xml.
> Action | Specify a name for the <profiler> element in server.xml and restart the server.
> See Also | Developer's Guide, chapter “Debugging J2EE Applications”. Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4005

> Severity | WARNING
> Description | An error occurred while creating the embedded Java Virtual Machine. The server will not start if this error occurs.
> Action | Ensure that the JDK configuration in the java-config element in server.xml points to a valid JDK. In particular, ensure that the JDK is installed in the directory path as specified in the java-home attribute. Restart the server.
> See Also | Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4007

> Severity | WARNING
> Description | A generic exception report occurred.
> Action | Refer to the messages logged along with this message to determine the cause of the error.

> ##### CORE4008

> Severity | WARNING
> Description | An error occurred while trying to load the Throwable class. As a result of this, context information about exceptions is not logged to the server log file.
> Action | If the problem persists, restart the server instance.

> ##### CORE4009

> Severity | WARNING
> Description | An error occurred while loading the embedded Java Virtual Machine. The server will not start if this error occurs.
> Action | Ensure that the JDK configuration of the java-config element in server.xml points to a valid JDK. In particular, ensure that the directory pointed by the java-home attribute is the directory path where JDK is installed. Restart the server.
> See Also | Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4011

> Severity | WARNING
> Description | An error occurred during initialization of the Java subsystem in the server. The server will not start if this error occurs.
> Action | Ensure that the server-classpath configuration of the java-config element in server.xml has not changed and does not contain any errors. Restart the server.
> See Also | Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4012

> Severity | WARNING
> Description | An error occurred during initialization of the Java subsystem in the server. The server will not start if this error occurs.
> Action | Ensure that the server-classpath configuration of the java-config element in server.xml has not changed and does not contain any errors. Restart the server.
> See Also | Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4013

> Severity | WARNING
> Description | An error occurred during initialization of the Java subsystem in the server. The server will not start if this error occurs.
> Action | Ensure that the server-classpath configuration of the java-config element in server.xml has not changed and does not contain any errors. Restart the server.
> See Also | Administrator's Configuration File Reference, chapter “Server Configuration Files”.

> ##### CORE4014

> Severity | WARNING
> Description | This error occurs when the Java subsystem is incorrectly configured in init.conf and obj.conf.
> Action | Ensure that the init-j2ee, ntrans-j2ee and error-j2ee server application functions are configured correctly. Restart the server.
> See Also | Developer's Guide to NSAPI, chapter “Predefined SAFs and the Request Handling Process”. Developer's Guide to NSAPI, chapter “SAFs in the init.conf file”

> ##### CORE4015

> Severity | WARNING
> Description | This error indicates insufficient memory allocation during the initialization of the Java subsystem.
> Action | Ensure that the system has sufficient memory and then restart the server.
> See Also | Release Notes, section “Software and Hardware Requirements”.

> ##### CORE5001

> Severity | SEVERE
> Description | An internal error occurred.
> Action | Analyze the System, as described on (more...) with the stack trace information

> ##### CORE5005

> Severity | SEVERE
> Description | An internal error occurred during dynamic resource deployment.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5007

> Severity | SEVERE
> Description | An internal error occurred during dynamic resource un-deployment.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5009

> Severity | SEVERE
> Description | An internal error occurred during dynamic resource re-deployment.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5011

> Severity | SEVERE
> Description | An internal error occurred while enabling the dynamic resource.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5013

> Severity | SEVERE
> Description | An internal error occurred while disabling the dynamic resource.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5014

> Severity | WARNING
> Description | An internal configuration error occurred.
> Action | Restart the server. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5015

> Severity | WARNING
> Description | An internal configuration error occurred.
> Action | Restart the server. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5016

> Severity | WARNING
> Description | An internal error occurred. For example, a null pointer exception occurred while loading the application.
> Action | Restart the server. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5017

> Severity | SEVERE
> Description | An error occurred while redeploying the application.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5018

> Severity | SEVERE
> Description | An error occurred during dynamic deployment of a connector module.
> Action | Analyze the System, as described on (more...) with stack trace information.

> ##### CORE5019

> Severity | SEVERE
> Description | An error occurred during dynamic reload of an application.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5020

> Severity | SEVERE
> Description | An error occurred during dynamic deployment of the EJB module.
> Action | Add all the necessary resources used by this EJB module and restart the server. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5021

> Severity | SEVERE
> Description | The application was not loaded during server startup or during dynamic deployment.
> Action | This is due to missing resources (JDBC, JMS, and so on). If the problem persists, Analyze the System, as described on (more...) with stack trace information.

> ##### CORE5028

> Severity | WARNING
> Description | An exception occurred while creating the time stamp for MIME types.
> Action | See the messages logged along with this message to determine how to fix the error.

> ##### CORE5029

> Severity | WARNING
> Description | An IO error occurred while setting the value of time stamp in a new file.
> Action | See the messages logged along with this message to determine how to fix the error.

> ##### CORE5030

> Severity | WARNING
> Description | Unsupported Javac option found in server configuration.
> Action | User configured invalid Javac option. Check the javac-options of java-config element in server.xml.

> ##### CORE5031

> Severity | SEVERE
> Description | An exception occurred while loading the license.
> Action | Analyze the System, as described on (more...) .

> ##### CORE5032

> Severity | SEVERE
> Description | An error occurred because the license file is invalid.
> Action | Analyze the System, as described on (more...) .

> ##### CORE5033

> Severity | SEVERE
> Description | The evaluation license for the Application Server has expired.
> Action | Contact the Sun Microsystems representative to obtain the software.
> See Also | The Sun Microsystems product upgrade site at http://www.sun.com/as7upgrade for Application Server product information and downloads.

> ##### CORE5034

> Severity | SEVERE
> Description | An error occurred while assigning remote permissions.
> Action | Analyze the System, as described on (more...) .

> ##### CORE5035

> Severity | SEVERE
> Description | An error occurred while setting up the instance limit.
> Action | Analyze the System, as described on (more...) .

> ##### CORE5036

> Severity | SEVERE
> Description | This error indicates that the license is invalid.
> Action | Contact the Sun Microsystems representative to obtain an upgrade.
> See Also | The Sun Microsystems product upgrade site at http://www.sun.com/as7upgrade for Application Server product information and downloads.

> ##### CORE5037

> Severity | SEVERE
> Description | The error indicates that the evaluation license is about to expire.
> Action | Contact the Sun Microsystems representative to obtain the software.
> See Also | The Sun Microsystems product site at http://www.sun.com/as7upgrade, for Application Server product information and downloads.

> ##### CORE5038

> Severity | SEVERE
> Description | This error indicates that the evaluation license has expired.
> Action | Contact the Sun Microsystems representative to obtain the software.
> See Also | The Sun Microsystems product site at http://www.sun.com/as7upgrade, for Application Server product information and downloads.

> ##### CORE5046

> Severity | SEVERE
> Description | An error occurred while loading the applications during server startup time.
> Action | Analyze the System, as described on (more...) with the stack trace information

> ##### CORE5047

> Severity | SEVERE
> Description | A configuration exception occurred while loading the applications during server startup time.
> Action | Analyze the System, as described on (more...) with the stack trace information

> ##### CORE5048

> Severity | SEVERE
> Description | A configuration exception occurred while retrieving the value of the dynamic reload enabled flag defined in server.xml.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5049

> Severity | SEVERE
> Description | An error occurred while shutting down applications.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5053

> Severity | SEVERE
> Description | An error occurred while terminating applications during server shutdown.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5054

> Severity | SEVERE
> Description | An error occurred while calling onReady state of the application life cycle.
> Action | Make sure the steady pools for the EJBs are created properly during server startup.

> ##### CORE5060

> Severity | WARNING
> Description | An error occurred while constructing a URL path for the classloader.
> Action | Check the classpath in server.xml. Verify if the files and directories you have specified are valid.

> ##### CORE5061

> Severity | WARNING
> Description | A generic exception occurred.
> Action | Refer to the exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5070

> Severity | SEVERE
> Description | Server context could not be created.
> Action | Refer to the exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5071

> Severity | SEVERE
> Description | An error occurred during initialization of the application server.
> Action | Refer to the exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5072

> Severity | SEVERE
> Description | An error occurred either during startup or while reconfiguring the application server.
> Action | Refer to the exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5074

> Severity | SEVERE
> Description | An error occurred while application server was shutting down.
> Action | Refer to exception data. to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5075

> Severity | SEVERE
> Description | An error occurred because the license file is invalid.
> Action | Obtain a valid license. Contact the Sun Microsystems representative to obtain the software.

> ##### CORE5080

> Severity | SEVERE
> Description | An exception occurred while resolving the initial reference of ORB. The lookup for RootPOA failed for the ORB started in the server.
> Action | The ORB was not created in the server. Analyze the System, as described on (more...) with the complete stack trace.

> ##### CORE5081

> Severity | SEVERE
> Description | The ORB was not created in the server.
> Action | Check the ORB properties in the server.xml file or check if the ORB listener port is already in use. If the problem persists, Analyze the System, as described on (more...) with the complete stack trace information.

> ##### CORE5082

> Severity | SEVERE
> Description | An exception occurred while running the J2EE services.
> Action | Server startup failed. Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5084

> Severity | SEVERE
> Description | An exception occurred while creating or binding the server object in the naming service.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5089

> Severity | SEVERE
> Description | An exception occurred while initializing the realmmanager and registering with the naming service.
> Action | Analyze the System, as described on (more...) with the stack trace information

> ##### CORE5090

> Severity | SEVERE
> Description | Unable to write to the seed1 file, for fast startup. The next startup is likely to be slow.
> Action | Refer to the exception data to understand the context of this log message. See the other log messages reported along with this message.

> 1A file used to store a random secure number. The application server stores this number in the file and accesses it whenever the server restarts.

> ##### CORE5091

> Severity | SEVERE
> Description | The J2EE server startup failed.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5092

> Severity | SEVERE
> Description | The J2EE server reported an error.
> Action | See the description of the error. Analyze the System, as described on (more...) with stack trace information.

> ##### CORE5093

> Severity | SEVERE
> Description | The J2EE server startup failed.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### CORE5094

> Severity | SEVERE
> Description | An exception occurred while looking up the server object during shutdown.
> Action | Refer to exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5095

> Severity | SEVERE
> Description | Unable to shutdown the J2EE server.
> Action | Refer to exception data to understand the context of this log message. See the other log messages reported along with this message.

> ##### CORE5096

> Severity | WARNING
> Description | Relative pathname is specified for transaction log directory.
> Action | Check the tx-log-dir attribute of transaction-service element in server.xml.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.