You can try setting the jms retry limit and error destination for auto moving the messages to the error queue.

http://download.oracle.com/docs/cd/E13222_01/wls/docs90/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html

Poison messages can be handled in a variety of ways, and there's a very nice three page discussion titled "Handling Poison messages" in the the JMS chapter of the book "Professional Oracle WebLogic Server".

The following might apply in your case:

- Configure a time-to-live override on the 3 original destinations, or programmatically set time-to-live in your application.

- Configure a Q called Timeout.

- Set the error destination for each destination to reference this Timeout Q.

- Configure an expiration policy for the destination (to redirect expired messages to the error destination instead of simply discard them).

- Configure a redelivery limit for the destination (max # of retries before messages are redirected to the error destination).

On the other hand, these days I try not to recommend depending on the "redelivery limit" option. The problem is that this limit applies to all types of delivery failures that can force a redelivery, not just specifically your "message format incorrect" problem. The best option, if its not too much work, might be to modify your application so that it detects incorrectly formatted messages, or messages that have a high JMSXDeliveryCount value, and sends them them to a designated queue (a "BadlyFormattedMessage" queue) instead of forcing redelivery or attempting to process them...

In addition, you may want to configure a "redelivery delay" to help prevent immediate redelivery of failed messages that can't be processed right away, but may be fine within a few seconds or a minute or so...

Hope this helps,

Tom

Edited by: TomB on Jun 21, 2010 6:43 PM

The type string that you use to obtain your connection should be either "weblogic.management.mbeanservers.runtime" or "weblogic.management.mbeanservers.domainruntime" depending on whether your trying to work with only runtime mbeans for a particular server (the former) or all runtime mbeans for the entire domain (the latter).

And if you're not familiar with how to find a particular mbean instance, an alternate approach is to get all instances of a particular type, you can use a wild card query such as:

rtConnection.queryMBeans(new ObjectName("*:Type=" + type + ",*"), null);

Where, if I recall correctly, type can be either "JMSDestinationRuntime" or "JMSServerRuntime" (which both have pause/resume methods).

Hope this helps,

Tom

Edited by: TomB on Jun 23, 2010 12:37 PM