javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
JVM requested a restart.
Wrapper Process has not received any CPU time for 194 seconds. Extending timeouts.
java.net.SocketException: Connection reset]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:168)
at javax.naming.InitialContext.lookup(InitialContext.java:292)
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.net.SocketException: Connection reset
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:286)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:606)
... 4 more
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:118)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at java.io.DataInputStream.readByte(DataInputStream.java:248)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:218)
... 8 moreWrapper Manager: The Wrapper code did not ping the JVM for 56 seconds. Quit and let the Wrapper resynch.
Wrapper Process has not received any CPU time for 24 seconds. Extending timeouts.
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.JVM requested a restart.
Wrapper Process has not received any CPU time for 84 seconds. Extending timeouts.
Wrapper Manager: The Wrapper code did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
Launching a JVM...
Startup failed: Timed out waiting for a signal from the JVM.------------------------------------------------------------------------
Advice:
The Wrapper consists of a native component as well as a set of classes
which run within the JVM that it launches. The Java component of the
Wrapper must be initialized promptly after the JVM is launched or the
Wrapper will timeout, as just happened. Most likely the main class
specified in the Wrapper configuration file is not correctly initializing
the Wrapper classes:
xylz.util.wrapper.WrapperStart
While it is possible to do so manually, the Wrapper ships with helper
classes to make this initialization processes automatic.
Please review the integration section of the Wrapper's documentation
for the various methods which can be employed to launch an application
within the Wrapper:
http://wrapper.tanukisoftware.org/doc/english/integrate.html
------------------------------------------------------------------------Wrapper Process has not received any CPU time for 168 seconds. Extending timeouts.
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.JVM did not exit on request, terminated
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
Wrapper Manager: The Wrapper code did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.javax.naming.NameNotFoundException: TpfClass not bound
JVM requested a restart.
Wrapper Process has not received any CPU time for 160 seconds. Extending timeouts.
at org.jnp.server.NamingServer.getBinding(NamingServer.java:490)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:498)
at org.jnp.server.NamingServer.getObject(NamingServer.java:504)
at org.jnp.server.NamingServer.lookup(NamingServer.java:277)
at org.jnp.server.NamingServer.lookup(NamingServer.java:251)
at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
JVM requested a restart.
只能看出来，问题的原因是因为：
TpfClass没有绑定在 rmi注册上。
JNDI是否已经正确配置。
由于找不到TpfClass，造成连接超时。
Wrapper Manager: The Wrapper code did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
Launching a JVM...
code did not ping the JVM for 30 seconds 应该是JVM出了问题。导致 has not received any CPU time for 84 seconds.84秒不能接收cpu 导致socket 或者是 inputstream 出了问题。也有可能是JVM的承载太大导致关闭可以考虑在两台电脑上装两个JVM负载均衡。先测试