Re: [xmlblaster] persistent connection behavior

[Michele <michele at laghi.eu>]

Hi John,
persistent connections and sessions only ensure that these are available 
again after a server crash recovery. The behavior you are expecting is 
the failsafe behavior described in the requirement:

http://www.xmlblaster.org/xmlBlaster/doc/requirements/client.failsafe.html

(of course together with the persistent sessions you already have).

Follow the instructions described at the end of the requirement. 
Basically retries=-1 (both for connections and callbacks), set a ping 
interval and a delay, choose positive sessionIds (always for the 
persistent sessions and subscriptions), configure the maxEntries for the 
callback and the connection queue and that should make it!

Regards
Michele


Horner, John wrote:
> I had always believed that if I had a persistent connection and 
> subscription that the server would remember me and what I had had 
> delivered if I lost my connection.
>
> We tried an experiment where we connected with a persistent connection, 
> made a persistent subscription, and then after a while unplugged the 
> ethernet cable to the client.  We expected that when we plugged back in 
> the cable that everyone would connect and pick right back up where we 
> left off.
>
> Perhaps I was naive.  Upon closer reading of the reference doc it only 
> claims that persistent connections survive server crashes, not general 
> loss of connection.  So, what exactly are the conditions across which a 
> persistent connection survives?
>
> Is there a good way to accomplish what we want (recommence delivery 
> automatically following any connection failure)?
>
> Thanks,
> John Horner
>
> Open Roads Consulting Inc.
> (757) 546-3401
> www.openroadsconsulting.com