RE: Re: OpenJMS 0.7.7-alpha-3 released

> From: Eric P.
> 
> After some tests with the simple client and our application, 
> it seems to work. 
> Wonderful :)
> 
> I have 3 more questions : 
> 
> - Do you confirm that only openjms-tunnel-0.7.7-alpha-3.war 
> has been modified by this fix?

No. There were also changes to openjms-net-0.7.7-alpha-3.jar 

> 
> - If we reconnect the client before the idlePeriod, the 
> problems reappears. How can i detect that the subscription 
> has failed on the createTopicSession in order to try a 
> reconnection? There is still no exception thrown. The client hangs.

Shouldn't do, if the server is using the updated openjms-net*.jar 
The durable subscriber won't be able to reconnect until 
the server has cleaned up the original connection however.
This will occur after idlePeriod seconds.

> 
> - To bypass this, i set the idlePeriod to 5s. Is there an 
> impact on performance, network traffic or connection 
> fiability? I would like to set idlePeriod to 2s, the shortest 
> time a client take to restart. Is it possible without effects?

Wouldn't do this. You're likely to lose your connection to the server
if your client or the network is overloaded.
As it is, if you are stepping through your client in a debugger,

Also be aware that you could lose the connection. If you want to avoid this,

disable connection reaping by setting idlePeriod to 0.
This only applies to the http connector. None of the other connectors
time out this way.

-Tim


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click