Hey schrouf, Thanks for the response....
I am using durable subscriptions and have considered cranking up the retries. But, I also like the idea of the DLQ. Monitoring that single queue for problems rather than X number of topics/subscribers. I have also been experimenting with using a message selector like: (retrysubscriber IS NULL OR retrysubscriber='myDurableSubscriber') and populating that retrysubscriber property from information contained in the JBOSS_ORIG_DESTINATION property of the DLQed message when I republish the message. This seems to be working well, but it feels kind of hackish. I'm beginning to think that if I care this much about specifying destination in specific situations then I should probably consider using queues for those cases. Regardless, at least I have some options... Thanks again. Brian. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827929#3827929";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827929>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
