Re: [xSocket-develop] FW: OnDisconnect is not being called in multiplex scenario
Status: Inactive
Brought to you by:
grro
|
From: Bhatnagar, V. (Ved) <vbh...@av...> - 2009-03-26 16:30:27
|
Yes, We did try it and still we do not get the OnDisconnect or any other exceptions in server side, when Client JVM is killed. Thank you, Ved From: Gregor Roth [mailto:gre...@gm...] Sent: Wednesday, March 25, 2009 12:35 PM To: Bhatnagar, Ved (Ved) Cc: xso...@li... Subject: Re: FW: OnDisconnect is not being called in multiplex scenario Hi Ved, did you already consult the xSocket Tutorial - Chapter 8 (http://xsocket.sourceforge.net/core/tutorial/V2/TutorialCore.htm)? Does this answer your questions? Gregor ----- Original Message ----- From: Bhatnagar, Ved (Ved) Sent: 25/03/09 07:06 am To: Gregor Roth Subject: FW: OnDisconnect is not being called in multiplex scenario Need your help . From: Bhatnagar, Ved (Ved) Sent: Monday, March 23, 2009 4:50 PM To: 'xso...@li...' Subject: OnDisconnect is not being called in multiplex scenario Hi, We are running a prototype to further our understanding of xScoket library. We are stuck in disconnect scenario testing. We have a simple Multiplexed client and a simple Multiplexed server using pipelines( code copied from samples provided in documentation). We are trying to see how to handle disconnects in following three scenarios. 1. Client does graceful close on pipeline. This Scenario is working as Server protocol handler invokes OnDisconnect for the correct pipeline. 2. Client crashes ( we kill the client JVM) .. This scenario is not working as Server protocol handler does not invoke any callbacks. 3. Network cable is unplugged between client and server. We have not yet tested it. Please advise as to how to handle such scenarios. Thank you, Ved / Bobby |