I found some interesting info in the spec:
section 6.2 of the jms spec:
http://java.sun.com/products/jms/docs.html
anonymous wrote : 
  | Pub/Sub Latency
  | Since there is typically some latency in all pub/sub systems, the exact
  | messages seen by a subscriber may vary depending on how quickly a JMS
  | provider propagates the existence of a new subscriber and the length of 
time a
  | provider retains messages in transit.
  | For instance, some messages from a distant publisher may be missed because 
it
  | may take a second for the existence of a new subscriber to be propagated
  | system-wide. When a new subscriber is created, it may receive messages sent
  | earlier because a provider may still have them available.
  | JMS does not define the exact semantics that apply during the interval when 
a
  | pub/sub provider is adjusting to a new client. JMS semantics only apply once
  | the provider has reached a ?steady state? with respect to a new client.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911811#3911811

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911811


-------------------------------------------------------
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
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to