RE: retry or poll interval

See inline.

> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> Of Furuvutu Furuvutu
> Sent: Friday, 16 September 2005 1:24 PM
> To: [email protected]
> Subject: [openjms-user] retry or poll interval
> 
> Hi!
> 
> 1) A JMS subscriber using OpenJMS seemed to "poll" the Open 
> JMS server at regular intervals.  Would anyone know the 
> default interval setting?

Not sure what you're asking. At the JMS API level, clients may
poll the server using the MessageConsumer.receive(long timeout) 
or MessageConsumer.receiveNoWait() methods. In both cases, the client
determines the interval.
The underlying communications protocols may periodically contact 
the server to determine the health of the connection. In 0.7.7, 
this occurs every 15 seconds or so if the physical connection is idle.

> 
> 2) Is there a retry limit?  If yes, what is the default 
> maximum retry limit?
> 
> 3) If a JMS subscriber maintains a session/connection to a 
> JMS server all the time, in order for it to receive updates 
> anytime, can this "polling" cause a network to slow down? or 
> the server to slow down? 

The most efficient means of receiving messages is to use
asynchronous messaging, by registering a MessageListener with
a MessageConsumer. Regular polling from multiple subscribers will
impact peformance.

> Approximately, there will be 300+ JMS subscribers.
> 
> Your answers/suggestions would be greatly appreciated.
> Thank you.

-Tim



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl