Re: [xmlblaster] Socket connection: warning after disconnect

[Marcel Ruff <mr at marcelruff.info>]

Hi Michael,

Michael Justin wrote:
> Dear all
>
> I have managed to replace the xml-rpc based protocol layer by a sockt 
> protocol implementation, however the disconnect give a warning and I 
> am not sure if this is a serious problem.
>
> It looks like xmlBlaster tries to read from the socket after the 
> client has sent the disconnect command. The protol entry says "Error 
> parsing TCP data from '/192.168.178.22:1076', check
> if client and server have identical compression or SSL settings: 
> java.net.Socket
> Exception: Software caused connection abort: recv failed".
>
> I have found this information about the disconnect: "The server sends 
> the response (ACK) immediately from the SOCKET layer. It can't send it 
> later because the socket is shutdown during server side disconnect." - 
> so do I understand correctly that the client should handle disconnect 
> in a different way? Currently it waits for an asynchronous response.
This is correct, if you start the server:

java -Dcom.sun.management.jmxremote org.xmlBlaster.Main 
-logging/org.xmlBlaster.util.protocol.RequestReplyExer FINEST 
-logging/org.xmlBlaster.util.protocol.socket.SocketExecutor FINEST 
-logging/org.xmlBlaster.util.xbformat.XbfParser FINEST

and a client

java HelloWorld3

you can see in the server log the disconnect response:

Successful sent response for disconnect() >       
145**R**1HelloWorld3:1210329399868000000*disconnect*sessionId:192.168.1.25-47897930-3**<qos><state 
id='OK'/></qos>**0*<

regards
Marcel
> Here is the full log:
>
> 2008-05-08 15:22:39.515  INFO   
> 13-XmlBlaster.SOCKET.tcpListener-Username RL10 o
> rg.xmlBlaster.authentication.SubjectInfo shutdown: 
> 2-/node/heron/client/Unittest
> s: Destroying SubjectInfo. Nobody is logged in and no queue entries 
> available
> 2008-05-08 15:22:39.515  FINE   
> 13-XmlBlaster.SOCKET.tcpListener-Username RL10 o
> rg.xmlBlaster.util.queue.ram.RamQueuePlugin shutdown: Entering 
> shutdown(0)
> 2008-05-08 15:22:39.515  FINE   
> 13-XmlBlaster.SOCKET.tcpListener-Username RL10 o
> rg.xmlBlaster.util.queue.ram.RamQueuePlugin shutdown: Entering 
> shutdown(0)
> 2008-05-08 15:22:39.515  FINE   
> 13-XmlBlaster.SOCKET.tcpListener-Username RL10 o
> rg.xmlBlaster.protocol.socket.HandleClient shutdown: Shutdown cb 
> connection to c
> lient/Unittests ...
> 2008-05-08 15:22:39.531 WARNING 12-XmlBlaster.SOCKET RL10 
> org.xmlBlaster.protoco
> l.socket.HandleClient run: 
> SOCKET-socket://192.168.178.22:7607-client/Unittests-
> /192.168.178.22:1076: Error parsing TCP data from 
> '/192.168.178.22:1076', check
> if client and server have identical compression or SSL settings: 
> java.net.Socket
> Exception: Software caused connection abort: recv failed
> 2008-05-08 15:22:39.531  FINE   12-XmlBlaster.SOCKET RL10 
> org.xmlBlaster.protoco
> l.socket.SocketDriver removeClient: Didn't find a client object to 
> remove: SOCKE
> T-socket://192.168.178.22:7607-client/Unittests-/192.168.178.22:1076
> 2008-05-08 15:22:39.531  FINE   12-XmlBlaster.SOCKET RL10 
> org.xmlBlaster.protoco
> l.socket.SocketDriver removeClient: Didn't find a client handle to 
> remove: SOCKE
> T-socket://192.168.178.22:7607-client/Unittests-/192.168.178.22:1076
> 2008-05-08 15:22:39.546  FINE   12-XmlBlaster.SOCKET RL10 
> org.xmlBlaster.protoco
> l.socket.HandleClient closeSocket: Closed socket for 'client/Unittests'.


--
Marcel Ruff
http://www.xmlBlaster.org
http://watchee.net
Phone: +49 7551 309371