I have a bean driven message that throws an exception under certain conditions. When it throws an exception, the message is not processed and is not returned to the queue. From what I understand with MQ and WAS (WebSphere Application Server), the message should be marked as bad after the number of attempts and removed from the queue. This does not happen, and the message remains in the queue marked as bad.
What part of the configuration in MQ and / or WAS did I skip to install the correct one?
(The problem with MDB metadata exceptions is NOT here)
Thank.
BOQNAME BOQTHRESH. , , .
, QMgr . , , MDB, .
MDB , . - , . , .
DLL . DLQ - , QMgr , QMgr, . " ", MDB, , . , DLQ. , DLQ.
BOQTHRESH 1 2, , QMgr , . BOQTHRESH 5 10, , . , , .
WebSphere .WAS 5, .
Source: https://habr.com/ru/post/1748004/More articles:CruiseControl.NET Build Tag Problem - .netEnable Grizzly to make a simple JaaS HTTP request - javaCombining EditText and Button? - androidHow can I bind WPF TreeView data to lazy and asynchronous? - asynchronousHow to use java.lang.Terminator correctly? - javaerror during build using builder builder sandcastle with Visual Studio 2010 .NET 4.0 project - visual-studio-2010SVN tortoise tree conflicts with itself - svnHow to draw a map from images? - c #UINavigationController changes the position of the pressed view. UIViewController - viewsInteresting behavior of LinqToSql - c #All Articles