I'm not following. Superficially,
I have a remote client that calls the method in server using sslscoket and both servers will successfully print out the echo
But If i try to call any method on 4.2.3 server from a remote client I will get a debug message about ...
seem to be contradictory. Could you clarify?
If I use 4.2.3 server I could see the socket exception in log file but if I use the same code in jboss-4.2.0.CR2 I don't see this in log file.
I see this exception as a DEBUG log message and it is not directly affecting my application(ie, does not throw this exception in TestFacadeBean.java or Client.java).
2008-12-29 23:56:09,504 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#2[192.168.1.60:58092] closing socketWrapper: ServerSocketWrapper[17576e1[TLS_DHE_DSS_WITH_AES_128_CBC_SHA: Socket[addr=/192.168.1.60,port=58092,localport=3843]].17576e1] 2008-12-29 23:56:09,504 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] unable to writing CLOSING byte java.net.SocketException: Connection closed by remote host at com.sun.net.ssl.internal.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1246) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:43) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1631) at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:666) at org.jboss.remoting.transport.socket.ServerSocketWrapper.close(ServerSocketWrapper.java:57) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:520) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) 2008-12-29 23:56:09,504 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] unable to close output stream 2008-12-29 23:56:09,504 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[17576e1[TLS_DHE_DSS_WITH_AES_128_CBC_SHA: Socket[addr=/192.168.1.80,port=58092,localport=3843]].17576e1] closing 2008-12-29 23:56:20,071 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 6000
The message is nothing to worry about, which is why it is logged at DEBUG level. When a socket is closed on the server side, an attempt is made to write a pair of bytes which are interpreted on the client side to mean that the connection should not be used. But if the client has already shut down ("java.net.SocketException: Connection closed by remote host"), then it doesn't matter if the pair of bytes can be written.