Failed to initialize java.io.EOFException

[samavedulark]

Hi,

I am using Jboss 5.1 AS. Remoting is 2.5.2SP2. I am getting below error consistantly.

2012-10-16 10:26:48,156 ERROR [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#2[10.15.17.16:57038]) WorkerThread#2[10.15.17.16:57038] exception occurred during first invocation

java.lang.reflect.InvocationTargetException

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

    at org.jboss.remoting.transport.socket.ServerThread.createServerSocketWrapper(ServerThread.java:937)

    at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:515)

    at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)

Caused by: java.net.SocketException: Connection reset

    at java.net.SocketInputStream.read(SocketInputStream.java:168)

    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

    at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)

    at java.io.BufferedInputStream.read(BufferedInputStream.java:317)

    at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266)

    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279)

    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)

    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)

    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)

    at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:100)

    at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:54)

    at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.java:75)

    at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.java:58)

    at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:199)

    at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:182)

    at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:67)

    at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:46)

    ... 7 more

2012-10-16 10:27:14,875 ERROR [org.jboss.invocation.pooled.server.ServerThread] (PooledInvokerThread-10.15.17.16-2) Failed to initialize

java.io.EOFException

    at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2281)

    at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750)

    at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780)

    at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280)

    at org.jboss.invocation.pooled.interfaces.OptimizedObjectInputStream.<init>(OptimizedObjectInputStream.java:147)

    at org.jboss.invocation.pooled.server.ServerThread.dorun(ServerThread.java:265)

    at org.jboss.invocation.pooled.server.ServerThread.run(ServerThread.java:156)

2012-10-16 10:27:18,609 ERROR [org.jboss.invocation.pooled.server.ServerThread] (PooledInvokerThread-10.15.17.16-4) Failed to initialize

java.io.EOFException

Any help is appreciable.

Thanks

RavZ

[samavedulark]

Hi,

Is anyone else facing this problem, it is happening quite frequently for us.

Thanks

Ravi S

[ron_sigal]

Hi Ravi,

Regarding the InvocationTargetException, that's a sign that the client died, or something like that.  Are you seeing any unusual behavior on the client side?

As for the EOFException, that's coming from the PooledInvoker transport, which isn't part of Remoting.  It lives in the Application Server, and I don't know a lot about it.  However, it looks like it might be due to the same problem that causing the InvocationTargetException, whatever that problem is.

-Ron