Cannot Produce a JVM Thread Dump After Server Crash

Issues Related to Applications

Cannot Produce a JVM Thread Dump After Server Crash

Description

If Enterprise Server crashes, the server dumps a core file and, by default, restarts with the-Xrs flag, which prevents the dump of a JVM thread dump.

Solution

To Obtain a Server Thread Dump

Type the following command:

asadmin generate-jvm-report --type=thread

See Also generate-jvm-report(1)

Issues Related to Applications

Error When Deploying EAR

Description

You tried to deploy a traditional EAR type of application in Enterprise Server but received an error message instead.

Solution

Enterprise Server v3 Prelude does not include a full EJB 3.0 implementation and does not support traditional EJB modules. Applications can be packaged for deployment in web archive (WAR) format only. You can download a partial implementation of a few EJB 3.1 features using Update Tool, but the bulk of EJB 3.0 (ejb-jar and .ear support) is not available . If you need a full Java EE 5 implementation, Sun Java System Application Server 9.1 (GlassFish v2) is a better choice for now. Web applications are the only Java EE application type supported by Enterprise Server v3 Prelude.

For related information, see the following:

Chapter 2 • Specific Issues

29

Page 29
Image 29
Sun Microsystems 820682310 Cannot Produce a JVM Thread Dump After Server Crash, Issues Related to Applications, Solution