Hi all, we encounter the same problem. I had a look at the DLQHandler sourcecode. There in the sendMessage-method it accesses the JMSDestination by invoking the messages's "getJMSDestination()". Then it tries to apply the "toString()" Method to that destination. But when you send a message from a non-JMS client (as we do) that field is null, because of the MQSeries internal header-mapping. I don't really know if we can call this a bug in JBoss. Because assuming we have a JMS-message is ok (and in a certain way we do have one). But it would be great to have a DLQHandler which does not discard a msg when it came from a c-client and an error processing it occured. I'm not quite sure if I should change the code at that point. It would be better if the people at jboss would do it.
Greets, helge <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827389#3827389";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827389>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
