| Author |
Message
|
| neadhelp2000 |
 Posted: Thu Jan 29, 2004 11:50 am Post subject: An internal WebSphere MQ error..... |
 |
|
Newbie
Joined: 29 Jan 2004
Posts: 7
|
Dear friends,
I am having WebSphereMQ v.5.3, Oracle 8.1.7 and JDK1.3.1 installed on WindowsXP-Professional (single system). Based on the steps as mentioned in the "Transactional Support - Oracle Configuration" (MQ System Administration guide), I tried to configure MQ to connect to Oracle. But upon restarting the following error occurs in the AMQERR01.LOG...
| Code: |
----- amqxfdcp.c : 660 --------------------------------------------------------
1/28/2004 13:40:33
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 0. This message is issued in association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 626 --------------------------------------------------------
1/28/2004 13:40:33
AMQ6184: An internal WebSphere MQ error has occurred on queue manager NIHK.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 1904.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 660 --------------------------------------------------------
|
Any clue to tackle this? Thanks for the help in advance.
Regards,
-Mike. |
|
| Back to top |
|
 |
| JasonE |
| Posted: Thu Jan 29, 2004 12:17 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Look for an FDC file (in the errors directory) named amq01904.0.fdc (or something like that). Post it in here if it doesnt help! |
|
| Back to top |
|
|
| neadhelp2000 |
| Posted: Thu Jan 29, 2004 1:39 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2004
Posts: 7
|
Thanks for the reply Jason.
I found the file AMQ01904.0.FDC and tried looking into it. Frankly speaking, I did not understand what it is saying. Is there any particular tool as such to view .FDC files (I used Notepad).
The contents of the file was too huge and I thought it would be improper to put it here. Is there any particular section of the file that you will need me to post?
Please help.
Thanks,
-Mike. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jan 29, 2004 1:40 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Put the top of the file here. It usually has a header followed by a stack trace. The header will work for starters. |
|
| Back to top |
|
|
| neadhelp2000 |
| Posted: Thu Jan 29, 2004 2:04 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2004
Posts: 7
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed January 28 13:40:32 Pacific Standard Time 2004 |
| Host Name :- KENNEDY (Windows XP Build 2600: Service Pack 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AQ123002 |
| Application Name :- MQM |
| Component :- aqqLoadMsgHdr |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Process :- 00001904 |
| Thread :- 00000004 |
| QueueManager :- NIHK |
| Major Errorcode :- arcE_OBJECT_DAMAGED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jan 29, 2004 2:07 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Jan 29, 2004 2:40 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
passing out free lunches? 
great job guys!!!
Michael |
|
| Back to top |
|
|
| neadhelp2000 |
| Posted: Thu Jan 29, 2004 4:19 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2004
Posts: 7
|
After I installed CSD05 I restarted the system. The following message was displayed in the Application Log of EventViewer.
| Code: |
The XA resource manager 'ORADB' was not available when called for xa_open. The queue manager is continuing without this resource manager.
The XA resource manager 'ORADB' has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. Normally this indicates that the resource manager has been shut down. In this case the resource manager cannot participate in any new transactions. Any in-flight transactions in which it was involved will be backed out, and any transactions in which it is in-doubt will only be resolved when contact with the resource manager is re-established. A further message will be issued when the queue manager has been able to do this. If the problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem.
Try to establish the reason why the resource manager is unavailable. It may be that an invalid XAOpenString has been defined for the resource manager in the 'qm.ini' configuration file. If this is the case, stop and then restart the queue manager so that any change will be picked up. Alternatively, the queue manager may be reaching a resource constraint with this resource manager. For example, the resource manager may not be able to accommodate all of the queue manager processes being connected at one time, you may need to alter one of its tuning parameters.
|
I tried to search for qm.ini on all the drives of my system and could not locate it.
The FDC file contains
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed January 28 13:40:32 Pacific Standard Time 2004 |
| Host Name :- KENNEDY (Windows XP Build 2600: Service Pack 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AQ123002 |
| Application Name :- MQM |
| Component :- aqqLoadMsgHdr |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Process :- 00001904 |
| Thread :- 00000004 |
| QueueManager :- NIHK |
| Major Errorcode :- arcE_OBJECT_DAMAGED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
|
Any clue??
Thanks a lot.
-Mike. |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Jan 30, 2004 6:53 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
That fdc is either old or without fp5 on:
| Quote: |
| | CMVC level :- p000-L021011 |
on mine:
| Quote: |
| | CMVC level :- p530-05-L030926 |
The -05- means fixpack level, the L* bit is build level (date, ie 2003 Sept 26th)
It also reports a damaged object, if you look at your queues, chances are one is damaged. As to the XA problem, pass... |
|
| Back to top |
|
|
| neadhelp2000 |
| Posted: Fri Jan 30, 2004 1:09 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2004
Posts: 7
|
I modified my MQ-XA settings and got the following (after restart):
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri January 30 12:36:34 Pacific Standard Time 2004 |
| Host Name :- MICHAELS (Windows XP Build 2600: Service Pack 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- TM046000 |
| Application Name :- MQM |
| Component :- tmiOpenResourceMgr |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00001556 |
| Thread :- 00000001 |
| QueueManager :- NIHK |
| Major Errorcode :- trcE_UNEXPECTED_RM_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ7605 |
| Probe Severity :- 2 |
| Probe Description :- AMQ7605: The XA resource manager Test2PC has returned |
| an unexpected return code -5, when called for xa_open. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 4294967291 fffffffb |
| Arith2 :- 1 1 |
| Comment1 :- Test2PC |
| |
| Comment2 :- xa_open |
| |
| Comment3 :- |
| |
| |
+-----------------------------------------------------------------------------+
|
I feel that the parameters that I specify in the QueueManager properties are in the wrong format. Can anyone help me in that.
Thanks,
-Mike. |
|
| Back to top |
|
|
|
|
