[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Once and only once delivery?

[timfox]

"adrian at jboss.org" wrote : I don't understand what you are trying to do?
  | 
  | To solve the original problem, you create a transacted session.
  | 

A local jms transaction doesn't work for the reasons I mentioned earlier in the thread, and which you mention here:

anonymous wrote : 
  | 
  | It is certainly true that for a local tx, you always have the problem
  | of the "transaction observer".
  | 
  | 1) create transacted session
  | 2) send 10 messages in the session
  | 3) commit the session
  | 
  | The problem being that (3) can work on the server but the network
  | connection fails just at this point, so the client gets a JMSException 
  | rather than the commited ok message.
  | 

anonymous wrote : 
  | Tracking messages ids isn't going to work, unless you
  | are prepared to hold all messages that were ever sent.
  | 

This is why I suggested having an expiry on them, so you only keep the ids for a maximum period of time.

Obviously this means that you can send duplicates of messages that were sent before that time, but as you point out this solution won't work 100% of the time unless you have an infinite amount of storage.



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

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