| Author |
Message
|
| shash |
 Posted: Tue Sep 05, 2006 1:39 pm Post subject: Pub-Sub Broker dies |
 |
|
Novice
Joined: 08 Dec 2004
Posts: 20
|
Hi,
We have been encountering a strange problem in our dev environment.
We use WebSphere MQ 5.3 CSD 12 on Win2K platform. Our client is WAS. We use MDBs as subscribers and support both durable and non-durable subscription.
We have a Queue Manager TESTQM and run a Pub-Sub broker on this QM.
After the QM is started, we bring up our Broker using
strmqbrk -m TESTQM
The broker starts to process messages and everything is fine.
After a while the broker dies and we see the following in our log file
----- amqxfdcp.c : 665 --------------------------------------------------------
09/01/2006 19:53:55
AMQ7159: A FASTPATH application has ended unexpectedly.
EXPLANATION:
A FASTPATH application has ended in a way which did not allow the queue manager
to clean up the resources owned by that application. Any resources held by the
application can only be released by stopping and restarting the queue manager.
ACTION:
Investigate why the application ended unexpectedly. Avoid ending FASTPATH
applications in a way which prevents WebSphere MQ from releasing resources held
by the application.
----- amqxfdcp.c : 631 --------------------------------------------------------
09/01/2006 19:53:55
AMQ6184: An internal WebSphere MQ error has occurred on queue manager TESTQM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1844.
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 : 665 --------------------------------------------------------
09/01/2006 21:27:37
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20805800. 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.
*******************
We then restart the broker. It works for a while and dies gain.
Does anyone have any idea as to what might be happening?
Best Regards |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Sep 05, 2006 1:40 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Did you get an *.FDC file? |
|
| Back to top |
|
|
| shash |
| Posted: Tue Sep 05, 2006 1:47 pm Post subject: |
|
|
Novice
Joined: 08 Dec 2004
Posts: 20
|
| Yes. The error I reported was extracted from AMQERR01.LOG which is under D:\apps\IBM\WebSphere MQ\Errors |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Sep 06, 2006 6:16 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| shash wrote: |
| Yes. The error I reported was extracted from AMQERR01.LOG which is under D:\apps\IBM\WebSphere MQ\Errors |
If you got an *.FDC file, then why don't you post the top of it here? These files are different than the AMQERR*.LOG files. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Sep 06, 2006 6:45 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bower5932 wrote: |
| If you got an *.FDC file, then why don't you post the top of it here? These files are different than the AMQERR*.LOG files. |
Also the output from the second command below:
| Code: |
cd /d "D:\apps\IBM\WebSphere MQ\bin"
"D:\apps\IBM\WebSphere MQ\bin\ffstsummary.exe" |
would be helpful. It looks like you may have more than one FDC. And these files are generally intended for use by IBM support engineers. Give them a call (maybe after you've posted the outputs here, and/or searched for the probe Id using "Search support" at http://www.ibm.com/software/integration/wmq/support/ ). |
|
| Back to top |
|
|
| shash |
| Posted: Wed Sep 06, 2006 9:45 am Post subject: |
|
|
Novice
Joined: 08 Dec 2004
Posts: 20
|
I am attaching the following - output of PCIVTRun, two FDCs and content of AMQ*.LOG
D:\apps\IBM\WebSphere MQ\Java\bin>PSIVTRun -nojndi -client -m TESTQM -host MYHOST -port 1450 -channel JAVA.CHANNEL -t
5648-C60, 5724-B41, 5655-F10 (c) Copyright IBM Corp. 2002. All Rights Reserved.
Websphere MQ classes for Java(tm) Message Service 5.300
Publish/Subscribe Installation Verification Test
Creating a Connection
Creating a TopicConnectionFactory
Creating a Session
Creating a Topic
Creating a TopicPublisher
Creating a TopicSubscriber
Creating a TextMessage
Adding text
Publishing the message to topic://MQJMS/PSIVT/Information
Waiting for a message to arrive [5 secs max]...
Got message:
JMS Message class: jms_text
JMSType: null
JMSDeliveryMode: 2
JMSExpiration: 0
JMSPriority: 4
JMSMessageID: ID:414d51205043503031202020202020206303ff4420000901
JMSTimestamp: 1157563401885
JMSCorrelationID:ID:414d51205043503031202020202020206303ff4420000605
JMSDestination: topic://MQJMS/PSIVT/Information
JMSReplyTo: null
JMSRedelivered: false
JMS_IBM_PutDate:20060906
JMSXAppID:TESTQM
JMS_IBM_Format:MQSTR
JMS_IBM_PutApplType:26
JMS_IBM_MsgType:8
JMSXUserID:PCMQUser
JMS_IBM_PutTime:17232191
JMSXDeliveryCount:1
A simple text message from the MQJMSPSIVT program
Reply string equals original string
Closing TopicSubscriber
Closing TopicPublisher
Closing Session
Closing Connection
PSIVT finished
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There were two FDCs
1)
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed September 06 10:17:47 Pacific Daylight Time 2006 |
| Host Name :- MYHOST (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005022 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\apps\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00001836 |
| Thread :- 00000001 |
| QueueManager :- TESTQM |
| Major Errorcode :- lrcW_S_FAST_PATH_APP_DEAD |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ7159 |
| Probe Severity :- 3 |
| Probe Description :- AMQ7159: A FASTPATH application has ended |
| unexpectedly. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2020 7e4 |
| Arith2 :- 7 7 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
zxcProcessChildren
xcsFFST
MQM Trace History
---} xllLongLockRelease rc=OK
--} apiUnlockQHandle rc=OK
--{ apiLockQHandle
---{ apiLockExclusive
----{ xllLongLockRequest
-----{ xllAccessMutexHandle
-----} xllAccessMutexHandle rc=OK
----} xllLongLockRequest rc=OK
---} apiLockExclusive rc=OK
--} apiLockQHandle rc=OK
--{ apiUnlockQHandle
---{ xllLongLockRelease
---} xllLongLockRelease rc=OK
--} apiUnlockQHandle rc=OK
--{ apiLockQHandle
---{ apiLockExclusive
----{ xllLongLockRequest
-----{ xllAccessMutexHandle
-----} xllAccessMutexHandle rc=OK
----} xllLongLockRequest rc=OK
2)
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed September 06 10:20:33 Pacific Daylight Time 2006 |
| Host Name :- MYHOST (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- KY322000 |
| Application Name :- MQM |
| Component :- Amqmsrvn :: WinMain |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- D:\apps\IBM\WebSphere MQ\bin\amqmsrvn.exe |
| Process :- 00001120 |
| Thread :- 00000001 |
| Major Errorcode :- OK |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Comment1 :- DCOM object configured with Interactive/Launching user |
| id |
| Comment2 :- Configure DCOM object to use specific user id |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xcsFFST
MQM Trace History
{ xcsGetWorkPath
} xcsGetWorkPath rc=OK
{ InitProcessInitialisation
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
} InitProcessInitialisation rc=OK
{ xcsCreateThreadMutexSem
} xcsCreateThreadMutexSem rc=OK
{ DLLMain
-{ MCSInitCriticalSection
-} MCSInitCriticalSection rc=OK
-{ InitializeGCS
--{ MCSInitCriticalSection
--} MCSInitCriticalSection rc=OK
-} InitializeGCS rc=OK
} DLLMain rc=Unknown(1)
{ xcsInitialize
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsGetNTUserName
-} xcsGetNTUserName rc=OK
-{ xcsGetNTOwnerSid
-} xcsGetNTOwnerSid rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
-{ xcsUpdateThreadUserDetails
--{ xcsGetNTOwnerSid
--} xcsGetNTOwnerSid rc=OK
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The AMQ*.LOG content
09/06/2006 10:17:47
AMQ7159: A FASTPATH application has ended unexpectedly.
EXPLANATION:
A FASTPATH application has ended in a way which did not allow the queue manager
to clean up the resources owned by that application. Any resources held by the
application can only be released by stopping and restarting the queue manager.
ACTION:
Investigate why the application ended unexpectedly. Avoid ending FASTPATH
applications in a way which prevents WebSphere MQ from releasing resources held
by the application.
----- amqxfdcp.c : 631 --------------------------------------------------------
09/06/2006 10:17:47
AMQ6184: An internal WebSphere MQ error has occurred on queue manager TESTQM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1836.
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 : 665 --------------------------------------------------------
09/06/2006 10:20: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.
Please let me know if it helps |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 06, 2006 12:24 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Not an answer, but can you run the application in bindings mode |
|
| Back to top |
|
|
| shash |
| Posted: Wed Sep 06, 2006 12:28 pm Post subject: |
|
|
Novice
Joined: 08 Dec 2004
Posts: 20
|
| Venela, my WebSphere Application server and WebSphere MQ run on different machines. So I am running in Client connection mode. |
|
| Back to top |
|
|
| shash |
| Posted: Wed Sep 06, 2006 2:54 pm Post subject: |
|
|
Novice
Joined: 08 Dec 2004
Posts: 20
|
| Another point to note is that I use terminal services client to connect to the WebSphere MQ server. When my terminal services session ends due to a time out or when I deliberately log out of my terminal service session, the broker dies. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Sep 06, 2006 3:10 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
|
|
