]
Ron Sigal updated JBREM-1017:
-----------------------------
Fix Version/s: (was: 2.2.2.SP7)
Improve socket timeout log message
----------------------------------
Key: JBREM-1017
URL:
https://jira.jboss.org/jira/browse/JBREM-1017
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.GA (Pinto), 2.2.2.SP8
Reporter: Takayoshi Kimura
Assignee: Ron Sigal
Fix For: 2.4.0.SP1, 2.2.2.SP9
Attachments: log.zip, testcase.zip
When tesing remoting compatibility between AS 4.0.5 and EAP 4.3.0.GA_CP01, I got the
following exception messages:
In server:
2008-07-22 22:55:57,281 ERROR
[org.jboss.remoting.serialization.impl.java.JavaSerializationManager]
java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion1_2(JavaSerializationManager.java:180)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:130)
at
org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:120)
at
org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:59)
at
org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:663)
at
org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:533)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
In client:
2008-07-22 22:55:57,178 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker]
Got marshalling exception, exiting
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:110)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1647)
at
java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1556)
at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1357)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:81)
at
org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:84)
at
org.jboss.invocation.unified.marshall.InvocationMarshaller.write(InvocationMarshaller.java:66)
at
org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:273)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
at org.jboss.remoting.Client.invoke(Client.java:525)
at org.jboss.remoting.Client.invoke(Client.java:488)
at
org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy1.remove(Unknown Source)
at com.redhat.jboss.support.support192039.TestClient.main(TestClient.java:39)
Actually it was just a socket timeout. However, there is no information for socket
timeout unless we set TRACE log level on org.jboss.remoting. Need more clearer log message
at least DEBUG level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: