|
Problem(Abstract) |
A bug in the Java™ 2 Software Developer Kit (SDK) related to the JIT
compiler can cause the administrative server process to hang in any
release of IBM® WebSphere® Application Server V5.0 when the JIT compiler
is enabled. |
|
|
|
Cause |
The symptoms of this problem are:
1. wsadmin using SOAP or RMI connectivity fails with the following
exception:
WASX7023E: Error creating "SOAP" connection to host "myhost";
exception
information: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed
out; targetException=java.io.InterruptedIOException: Read timed out]
WASX7213I: This scripting client is not connected to a server
process;
2. The administrative console hangs. If you turn on dmgr
trace, you see the following exception in the trace.log:
[11/11/03 11:06:15:104 EST] 6bdd35d8 HttpConnectio d There is no
process
to read data written to a pipe.
java.io.IOException: There is no
process to read data written to a pipe.
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java(Compiled
Code))
3. During the hang condition, javacores are not generated when
a kill -3 is issued on the administrative server process.
This problem is caused by a JIT-related bug in the Java 2 SDK. |
|
|
Resolving the
problem |
There are two possible solutions to this problem:
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|