| Author |
Message
|
| Satsuma |
 Posted: Tue Apr 27, 2010 10:48 pm Post subject: FDC's after changing queue props to GET_INHIBITED |
 |
|
Apprentice
Joined: 30 Apr 2007
Posts: 25
Location: Finland
|
Hi all,
we were testing some exceptions and when setting the queue to GET_INHIBITED in the middle of testing process the queue manager started throwing FDC's and collapsed. It was an XA-client connection which was reading the messages.
Have you any idea why this happened?
Seems like the failing process was amqrmppa. MQ version 7.0.1.0, win 2003 SP2.
-S |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Apr 28, 2010 12:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What's Probe ID in the head of the FDC files?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Satsuma |
| Posted: Wed Apr 28, 2010 12:50 am Post subject: |
|
|
Apprentice
Joined: 30 Apr 2007
Posts: 25
Location: Finland
|
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 28, 2010 1:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And you have Googled it or checked the IBM Support site to see whether it provides any information, or raised a PMR if not?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Satsuma |
| Posted: Wed Apr 28, 2010 1:43 am Post subject: |
|
|
Apprentice
Joined: 30 Apr 2007
Posts: 25
Location: Finland
|
| Yes, that's what I've done and nothing found. I guess the next step is a PMR. |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Apr 28, 2010 5:35 am Post subject: Re: FDC's after changing queue props to GET_INHIBITED |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Satsuma wrote: |
| ..when setting the queue to GET_INHIBITED in the middle of testing process.. |
Which queue is this?
| Satsuma wrote: |
| ..the queue manager started throwing FDC's and collapsed. |
Can you paste the first block and some following stanza from the FDC?
_________________
Regards
Sumit |
|
| Back to top |
|
|
| Satsuma |
| Posted: Wed Apr 28, 2010 8:55 pm Post subject: |
|
|
Apprentice
Joined: 30 Apr 2007
Posts: 25
Location: Finland
|
Hi,
it's just a normal local queue from which an XA-client is getting messages.
Here's the start of the FDC:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- tu April 27 2010 16:43:24 FLE Daylight Time |
| UTC Time :- 1272375804.521000 |
| UTC Time Offset :- 60 (FLE Daylight Time) |
| Host Name :- Localhost1 |
| Operating System :- Windows Server 2003, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZS402020 |
| Application Name :- MQM |
| Component :- zstAsyncConsume |
| SCCS Info :- lib/zst/amqzstd0.c, 1.199 |
| Line Number :- 1330 |
| Build Date :- Aug 13 2009 |
| CMVC level :- p000-L090813 |
| Build Type :- IKAP - (Production) |
| UserID :- UserId1 |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqrmppa.exe |
| Addressing mode :- 32-bit |
| Process :- 00003868 |
| Thread :- 00000036 |
| QueueManager :- QMGR1 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 152 |
| Last HQC :- 1.0.0-161960 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- krcE_UNEXPECTED_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
zstAsyncConsumeThread
zstAsyncConsume
xcsFFST
rc=lpiRC_WAITCANCELLED_ASYNCCONSUME
rc=MQRC_GET_INHIBITED
rc=MQRC_SYNCPOINT_NOT_AVAILABLE |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 29, 2010 1:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are doing an XA transaction and this is what the FDC is showing:
| Code: |
| rc=MQRC_SYNCPOINT_NOT_AVAILABLE |
So if sync point is not available what are you doing with an XA transaction?
Is this by any chance a multiphase commit as an MQ client connection without the ETC client?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Apr 30, 2010 2:11 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| fjb_saper wrote: |
You are doing an XA transaction and this is what the FDC is showing:
| Code: |
| rc=MQRC_SYNCPOINT_NOT_AVAILABLE |
So if sync point is not available what are you doing with an XA transaction?
Is this by any chance a multiphase commit as an MQ client connection without the ETC client? |
Being dumped from within an amqrmppa, it isn't that clear what this rc means in this context. I think the OP hasn't done anything to cause this, and should raise this with IBM. |
|
| Back to top |
|
|
|
|
