Strange rmi errors in server.log
lexus Nov 5, 2002 4:50 AMI use jboss 3.0.4RC1 week old from CVS (not updated to 3.0.4 release yet) My servlet (resided in different jvm) calls CMP1.1 entity bean that has byte[] as one of CMP fields (may be it is essential...). From time to time I face the following exception:
===========server.log===============
...
2002-11-04 18:28:02,454 ERROR [STDERR] java.lang.IllegalStateException: Task already scheduled or cancelled
2002-11-04 18:28:02,455 ERROR [STDERR] at java.util.Timer.sched(Timer.java:316)
2002-11-04 18:28:02,455 ERROR [STDERR] at java.util.Timer.schedule(Timer.java:128)
2002-11-04 18:28:02,456 ERROR [STDERR] at sun.rmi.transport.DGCAckHandler.startTimer(DGCAckHandler.java:84)
2002-11-04 18:28:02,456 ERROR [STDERR] at sun.rmi.transport.ConnectionOutputStream.done(ConnectionOutputStream.java:82)
2002-11-04 18:28:02,456 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.releaseOutputStream(StreamRemoteCall.java:94)
2002-11-04 18:28:02,456 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:302)
2002-11-04 18:28:02,456 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.java:148)
2002-11-04 18:28:02,456 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
2002-11-04 18:28:02,457 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
2002-11-04 18:28:02,457 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
2002-11-04 18:28:02,457 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
2002-11-04 18:28:02,457 ERROR [STDERR] at java.lang.Thread.run(Thread.java:536)
...
===========server.log===============
At client's (servlet's) side I see:
[2002-11-04 18:28:02,455,ImageServlet] javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
java.net.SocketException: Connection reset by peer: Connection reset by peer]
javax.naming.CommunicationException. Root exception is
java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:
java.net.SocketException: Connection reset by peer: Connection reset by peer
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:464)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:443)
at com.caucho.naming.LinkProxy.createObject(LinkProxy.java:127)
at com.caucho.naming.ContextImpl.dereference(ContextImpl.java:540)
at com.caucho.naming.ContextImpl.lookup(ContextImpl.java:173)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.tw.imgfactory.servlet.ImageServlet.getImageRemoteHome(ImageServlet.java:85)
at com.tw.imgfactory.servlet.ImageServlet.doGet(ImageServlet.java:37)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:126)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:103)
at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:96)
at com.caucho.server.http.Invocation.service(Invocation.java:312)
at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135)
at com.caucho.server.http.RunnerRequest.handleRequest(RunnerRequest.java:342)
at com.caucho.server.http.RunnerRequest.handleConnection(RunnerRequest.java:272)
at com.caucho.server.TcpConnection.run(TcpConnection.java:137)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.net.SocketException: Connection reset by peer: Connection reset by peer
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:116)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at java.io.DataInputStream.readByte(DataInputStream.java:276)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:189)
... 19 more
From that jboss-side exception occurs earlier, I conclude that "Connection reset by peer" on client-side is caused by jboss-side rmi exception. Can anybody help me with this?
Best wishes,
Alexei Yudichev