| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ 7\WAS 7.0.0.13 - MDB Rollback issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| CrashJohn |
 Posted: Thu May 26, 2011 1:41 am Post subject: MQ 7\WAS 7.0.0.13 - MDB Rollback issue |
 |
|
Novice
Joined: 04 Jun 2006
Posts: 21
|
Hi All,
We recently upgraded our Dev environment from MQ v6 to v7.0.1.4 and WAS from 7.0.0.7 to 7.0.0.13. We are in the process of testing all our existing solutions to make sure they are working after the upgrade.
We face an issue with one particular case, where in the MDB rolls back a message in case of MQ Exceptions and the listener is stopped. Ideally (before the upgrade), the message should be rolled back to WAS Input Queue. But after the upgrade to MQ 7, the rolled back message ends up in the SYSTEM.DEAD.LETTER.QUEUE (error message: mqrc 2362 - MQRC_BACKOUT_THRESHOLD_REACHED).
We tried incrementing the threshold of WAS Input Queue to '1' and set a backout Queue, to check if it can reach the Backout Queue instead of the Dead letter Queue. But it still ends up in SYSTEM.DEAD.LETTER.QUEUE with the same message (backout threshold reached).
Any pointers on resolving this issue? Is there a compatibility problem with MQ 7 and WAS 7.0.0.13?
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu May 26, 2011 2:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you opened a PMR on this? This may be dictated by the WAS level and not the MQ level. (Was has a corresponding MQ level depending on the fix pack). There have been a lot of fixes in the JMS area on the latest releases of MQ. You may have to upgrade to the latest fix pack of WAS, if you're not already there. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| CrashJohn |
| Posted: Thu May 26, 2011 4:39 am Post subject: |
|
|
Novice
Joined: 04 Jun 2006
Posts: 21
|
Yet to open a PMR with IBM. Thought I would check out here first before I raise a PMR.
Currently, WAS is at 7.0.0.13 and MQ at 7.0.1.4. Will probably need to upgrade WAS to the latest fixpack based on the feedback from IBM.
Thanks. |
|
| Back to top |
|
|
| CrashJohn |
| Posted: Fri Jun 03, 2011 12:57 am Post subject: |
|
|
Novice
Joined: 04 Jun 2006
Posts: 21
|
This issue is resolved.
Cause:
It looks like the WebSphere MQ JCA resource adapter version was not in sync with the WAS version 7.0.0.13. As per the below IBM article, the MQ resource adapter version should be at 7.0.1.3 (7.0.1.3-k701-103-100812) for WAS 7.0.0.13 but it was at 7.0.0.1 (7.0.0.1-k700-L081114)
http://www-01.ibm.com/support/docview.wss?uid=swg21248089
Resolution:
I manually updated the resource adapter through the WAS console for each server to the correct version (i.e. 7.0.1.3 - 7.0.1.3-k701-103-100812) and restarted all the servers.
After the restart, the solution is working as expected. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
