ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » How to use the backout feature

Post new topic  Reply to topic
 How to use the backout feature « View previous topic :: View next topic » 
Author Message
prash
PostPosted: Wed Jan 28, 2004 5:12 am    Post subject: How to use the backout feature Reply with quote

Newbie

Joined: 26 Nov 2003
Posts: 6

Hi all,
I have written a sample message driven bean, which simple rollsback the message by calling setRollbackOnly() on the txnContext. What i'm trying to achieve is after 4 such rollbacks(i.e message is redelivered 4 times) , the system should move the message to another queue. For this i configured my queue with a backout queue name and backout threshold. The system rollsback the message and after 4 attempts it indeeds moves the message to the backout queue. The problem is while it rollsback the message it thows a weired JMSException as given below :

[1/28/04 16:50:28:421 GMT+05:30] 3650f550 SystemOut O Inside the JMS Exception block with jms message Rolling back the current transaction.
[1/28/04 16:50:33:421 GMT+05:30] 28957542 JMSExceptionL W WMSG0018E: Error on JMSConnection for MDB JMSTester , JMSDestination jms/jmsTesterQ : javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: {0}
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1583)
at java.lang.Thread.run(Thread.java:512)

The connection has been configured with XA option.

My environment is MQ 5.2 and websphere application server 5.0

The MQ documentation unfortunately does not say anything about MQJMS1016.

Any inputs etc.
Back to top
View user's profile Send private message
bower5932
PostPosted: Wed Jan 28, 2004 6:49 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

First, I'd suggest that you move forward from MQ 5.2 (which is no longer supported) to WMQ 5.3. You are probably using a version of the MA88 classes, and there have been a lot of changes that you don't have.

Second, this looks like the kind of exception that would throw an *.FDC file. Do you have anything in your mq\errors subdirectory?
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
prash
PostPosted: Thu Jan 29, 2004 8:48 pm    Post subject: Reply with quote

Newbie

Joined: 26 Nov 2003
Posts: 6

Hi,
Unfortunately i cannot ask our clients to go for a new version of MQ as there are other applications using it.I do have FDC files in mq/error dir.The contents is given as under

+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Fri December 05 15:33:28 India Standard Time 2003 |
| Host Name :- IND-SPZ7W2S0098 (NT Version 5.0 Build 2195: Service |
| Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- XY315147 |
| Application Name :- MQM |
| Component :- xcsTimedLookupAccountName |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\PROGRA~1\MQSeries\bin\ENDMQM.exe |
| Process :- 00001376 |
| Thread :- 00000968 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal MQSeries error has occurred |
| (WinNT error 1352 from LookupAccountSid.) |
| Comment1 :- WinNT error 1352 from LookupAccountSid. |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Fri December 05 15:33:58 India Standard Time 2003 |
| Host Name :- IND-SPZ7W2S0098 (NT Version 5.0 Build 2195: Service |
| Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- XY334103 |
| Application Name :- MQM |
| Component :- xcsCheckLocalGroup |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\PROGRA~1\MQSeries\bin\ENDMQM.exe |
| Process :- 00001376 |
| Thread :- 00000968 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal MQSeries error has occurred |
| (WinNT error 2226 from NetLocalGroupGetInfo.) |
| Comment1 :- WinNT error 2226 from NetLocalGroupGetInfo. |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Fri December 05 15:34:29 India Standard Time 2003 |
| Host Name :- IND-SPZ7W2S0098 (NT Version 5.0 Build 2195: Service |
| Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- XC001009 |
| Application Name :- MQM |
| Component :- xcsInitialize |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\PROGRA~1\MQSeries\bin\ENDMQM.exe |
| Process :- 00001376 |
| Thread :- 00000968 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred (0) |
| |
+-----------------------------------------------------------------------------+

Do i need to apply some kind of update patch on it or is there some kind update frquired for the mq java libs . Where could i get the latest classes for MQ 5.2 ( i tried using jars which come with ver 5.3 of QM, but in that case the application simply doesen't run.

Thanks in advance
Back to top
View user's profile Send private message
bower5932
PostPosted: Fri Jan 30, 2004 6:11 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

Your FDCs are from December, and they are related to problems with endmqm. I don't think they have a thing to do with your current MDB problems.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
prash
PostPosted: Sun Feb 01, 2004 8:10 pm    Post subject: Reply with quote

Newbie

Joined: 26 Nov 2003
Posts: 6

Hi,
I took inputs from the first reply (a possibility of jar being of older versions) and landed at this location
http://www.developer.ibm.com/tech/faq/results/0,1322,1%253A401%253A407%253A36%253Amqjava,00.html#q36

This link took me to the following page to download the jar files
https://www6.software.ibm.com/dl/wsmqcsd/wsmqcsd-p
where i finally downloaded
"WebSphere Embedded Messaging interim fixes for WebSphere Application Server V5.0.2"

I applied the new jar and surprisingly it worked, and the exceptions are not coming at the same time the messages gets redirected to the backout queue after N number of failure attempts.
Also i noticed that on 5.2 if you specify a backout queue name then i get the exception message, as soon as i remove the backout queue name from the queue deinition i exceptions stopped appearing.

Howver i could not fully understand why it worked cos the link says that the jars are for MQ ver 5.3

Could you pls given your inputs on that. Should i recommend this jar for the production environment too.

Thanks a lot for your inputs
Regards
Prash
Back to top
View user's profile Send private message
bower5932
PostPosted: Wed Feb 04, 2004 8:24 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I'm not sure that I'm 100% clear on what you've tried/haven't tried and why things are working/not working. However, I can tell you that MQ 5.2 went out of support and you shouldn't be recommending this to your customers in a production environment. They should be using WMQ 5.3.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » How to use the backout feature
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.