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

> ## Chapter 18
> Lifecycle Module

> This chapter lists error messages that originate from the lifecycle module.

> ##

> LCM

> The lifecycle module listens and performs tasks in response to events in the server life cycle. These modules are automatically initiated at server startup and are notified at various phases of the server life cycle.

> ##### LCM0101

> Severity | FATAL
> Description | An error occurred while loading the server’s life cycle listener module.
> Action | Make sure that the life cycle module is in the server classpath. The classpath for the life cycle modules is configurable via the server-classpath attribute or the classpath of the lifecycle-module element. You can also place the JAR file classes in the <install-root>/domains/server1/lib/ or the classes in <install-root>/domains/server1/classes.
> See also | Developer’s Guide, chapter “Developing Lifecycle Listeners”.

> ##### LCM0103

> Severity | FATAL
> Description | The server is not able to startup due to an error loading a life cycle module. This occurs when the is-failure-fatal attribute is set to true and there is an error loading the module.
> Action | Fix the error and restart the server. You can also set the is-failure-fatal attribute in server.xml to false. The server then ignores the error and continues the initialization and startup.
> See also | Developer’s Guide, chapter “Developing Lifecycle Listeners”.

> ##### LCM0105

> Severity | FATAL
> Description | An exception occurred when the server was setting up the life cycle module environment prior to invoking the module. This exception occurs due to an internal error.
> Action | Refer to the stack trace in the exception. This indicates the reason why the internal error occurred. Restart the server instance. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### LCM0107

> Severity | FATAL
> Description | An exception occurred when the server was resetting the life cycle module environment after invoking the module. The exception occurs due to an internal error.
> Action | Examine the exception stack and restart the server instance. If the problem persists, Analyze the System, as described on (more...) with the stack trace information.

> ##### LCM0201

> Severity | WARNING
> Description | A general exception occurred while running the life cycle module.
> Action | Examine the exception stack and rectify the life cycle module code or the root cause of the exception.

> ##### LCM0203

> Severity | WARNING
> Description | An exception, ServerLifecycleException occurred while running the life cycle module.
> Action | Examine the exception stack and rectify the root cause of the exception.

> ##### LCM0205

> Severity | FATAL
> Description | The server is about to shutdown while executing the life cycle modules. An exception stack trace may appear before this message.
> Action | 3. If the exception stack trace is available, examine the exception stack and rectify the root cause of the exception. 4. Examine the is-failure-fatal attribute in server.xml to see if the server can continue with these exceptions.

> Previous Contents Index Next

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