Great suggestions - I will give them more rigorous thought... Off the cuff, I believe I still have concerns though. In my situation, retaining message order is critical. That is why I had hoped to disable (or undeploy?) the bean. This would reduce load on the system by not having to shuffle these messages around while we are in an error state. The onus would be on an operator (or a JMX bean) to reactivate/reenable/redeploy the bean when the problem has been rectified.
I don't know if it is possible to setup lucsky's DLQ solution to retain my queue order. I believe that javadin's solution may also have the ordering problem. So, any additional thoughts? Thanks for your input!!! Cheers, Erik View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849885#3849885 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849885 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
