[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-126 -- JMS expiration

[timfox]

"weston.price at jboss.com" wrote : Ahhh wait... I see. Sorry, I'm a tool.
  | 
  | anonymous wrote : 
  |   | a) A RuntimeException is thrown from onMessage and ack mode = auto ack or dups ok, retry is immediately attempted (in JBM code). 
  |   | 
  | 
  | This is a bit different. I believe in the case of a transacted session the MessageCallbackHandler does nothing correct? It sounds like you are talking about JBM handling non transacted scenarios for DLQ. 
  | 
  | 

If a RuntimeException is thrown from onMessage and the session is transacted it is ignored as per JMS spec and delivery of the next message continues.

Perhaps we should have an option to turn off JCA dlq functionality if we know the provider supports its own? Should this be the default?


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

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