In order to capture the messages during exceptions we have used DLQ. we have implemented MDBs to subscribe for messages. when the DLQ reaches its maximum limit, the container (JBoss) goes into a loop posting for the message. we found that it is due to the fact that DLQ reaches its maximum depth and is not able to accommodate additional messages.
So I would like to know how to make the container stop posting for the message once the dead letter queue (DLQ) reaches its maximum depth. If you have any better suggestions to overcome this problem please advise me. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3908843#3908843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3908843 ------------------------------------------------------- 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
