|
| Problem | Work Load Management (WLM) across clones fails after a native Java StackOverFlowError occurs with a stand-alone enterprise java bean (EJB) client using multi-threading.
Problem:
If you follow all the steps outlined in the Technote entitled "WLM Enabling an EJB Java client for WAS 3.5.4+", and then perform WLM tracing on the client side outlined in this document for further problem determination, the trace would reveal that WLM was not being initialized. The tracing however does not indicate why.
To determine the problem, modify the client traceString to add ORB tracing for further problem determination:
"com.ibm.ejs.wlm.*=all=enabled:ORBRas=all=enabled" and specifying comm and debug trace in the java command line arguments of the client: java -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true.
After running this trace, the client side trace will reveal that while trying to initialize the WLM client implementation a stackoverflow exception is occuring:
[02.10.21 06:42:46:799 CDT] 1c7d42f ORBRas E 06:42:46.784
com.ibm.CORBA.iiop.PluginRegistry ijavaorb WorkloadThread: 3 ORBRas
loadPlugins () - 1 caught Throwable Exception. The exception is
java.lang.StackOverflowError
| | Cause | The native java stack was being overflowed. | | Solution | Resolution to the StackOverflowError is to increase the native stack to -Xss256k, the default is 128K. This can be increased through java command line argument as follows:
java -Xss256k
| |
| | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Workload Management (WLM) Operating system(s): Multi-Platform Software version: 3.5.6 Software edition: Advanced Reference #: 1141838 IBM Group: Software Group Modified date: 2003-10-27
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|