[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] detecting an 'ungraceful' disconnect on another client

Andrew.Yinger at Altarum.org wrote: 
is this a recent code change i need to get (via subversion) or is it in the
current release?


all releases, this exists since decades ... ;-)

http://www.xmlblaster.org/xmlBlaster/doc/requirements/client.configuration.html#callback

Marcel


Andrew.Yinger at Altarum.org wrote:

Hi, on my Java clients, I am currently using '__sys__UserList',
'__sys__Login' and '__sys__Logout' events to see who is logged in.
The problem is, sometimes  a client may ungracefully disconnect, and I
don't get a logout event until about 45-50 seconds later.  Are there some
ping, timeout, or session settings I can change so that I can detect an
ungraceful disconnect sooner?

I have tried:

dispatch/callback/plugin/socket/responseTimeout=8000
session.timeout=3000
connect/qos/sessionRefresh=true
dispatch/connection/pingInterval=900


... but cannot seem to figure out the right settings.

Thanks,
Andrew



Hi Andrew,

please try

   java org.xmlBlaster.Main

and

   java javaclients.HelloWorldSubscribe -dispatch/callback/pingInterval
1000

if you now kill the client with Ctrl-C the server will detect it
in 1 second (1000 millis), you can set it to any value you like

regards
Marcel

--
http://www.xmlBlaster.org






--
http://www.xmlBlaster.org