[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Ordering Group -- Transaction Scenario Analysis (Typical

[gaohoward]

"jhalliday" wrote : anonymous wrote : In this case, even the success of this commit doesn't mean that M1 is completed regarding ordering group rule, Simply because there may be other XA resources (XAResDB in this case) whose commit() may fail. JMS must not permit the deliver of M2 at this point of time and must be always aware of any recovery in the future. This means JMS server should not forget the M1 at this point.
  | 
  | I respectfully disagree with that view. What you are suggesting is basically building automated heuristic outcome handling into the resource manager. It's incredibly difficult to do in a robust and correct manner and it's simply not worth the overhead.
  | 
  | That said, there may, depending on the the isolation level used by the db, be a limited benefit to blocking M2 until an afterCompletion notification, provided it's done using in-memory (i.e. transient) data only.

I agree. I'll go first the simple one. That is we forget M1 after the commit() on JMS XA resource and deliver M2. 

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

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