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

[weston.price@jboss.com]

A rudimentary implementation would be fairly straightforward. Something along the lines of sending them off to the DLQ or a specified expiration destination. 

Is the JBM DLQ always active? I am a bit confused about the 'two' DLQ implementations and which one takes precendence. Does JBM do DLQ handling even with the existence of a connection consumer for a connection? 

Maybe we should think about 'uniting' these. Either that or I am just missing something (more likely).

The MDB container in the case of JCA inflow pretty much does nothing in terms of DLQ handling, transactions etc. This is all handled on my end. Basically the JMS/JCA adapter unifies the old ASF and JMSContainerInvoker functionality. 

The JCA DLQ handler detects redelivery attempts and either allows onMessage() to execute or shuffles the  message off to the DLQ which is specified as a property of the ActivationSpec. This is where the expiry stuff happens as well. 







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

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