| Author |
Message
|
| RogerLacroix |
 Posted: Thu Feb 19, 2004 2:05 pm Post subject: FDC problem |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
One of my clients queue managers started getting the following FDCs today (see bottom).
Specs:
- Solaris 8
- MQ 5.3 CSD3
Any help would be appreciated. Note: This box is heavily used by WebLogic client applications.
Regards,
Roger Lacroix
+---------------------------------------------------------------------------
|
| WebSphere MQ First Failure Symptom Report
| =========================================
|
| Date/Time :- Thursday February 19 15:29:07 EST 2004
| Host Name :- wghapp1d (SunOS 5.
| PIDS :- 5724B4103
| LVLS :- 530.3 CSD03
| Product Long Name :- WebSphere MQ for Sun Solaris
| Vendor :- IBM
| Probe Id :- AT041030
| Application Name :- MQM
| Component :- atxStart
| Build Date :- Mar 3 2003
| CMVC level :- p530-CSD03J
| Build Type :- IKAP - (Production)
| UserID :- 00001051 (mqm)
| Program Name :- amqzlaa0_nd
| Process :- 00004729
| Thread :- 00000036
| QueueManager :- CIBOTSQ
| Major Errorcode :- arcE_XAER_PROTO
| Minor Errorcode :- OK
| Probe Type :- INCORROUT
| Probe Severity :- 2
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred.
| FDCSequenceNumber :- 0
|
+---------------------------------------------------------------------------
MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessXARequest
zlaXAStart
zsqXAStart
kpiSyncPoint
apiSyncPoint
atmSyncPoint
atxStart
xcsFFST
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Thu Feb 19, 2004 2:27 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Roger i havent come accross this myself but here are some pointers.
1) Looking at the stack trace it looks like there is transactional activity going on an that you have a globally co-ordinated UOW by an XA agent. Since you say you have weblogic also involved, the first thing that comes to my mind is whether the transactional stuff is being handled properly.
2) Next best thing to do is to find out if there were any Events pertaining to the UOW/XA. Since you did not mention, i am not sure who is the Transaction co-ordinator here. But in any case, for each TC you would have a log or event log where all the errors/info for the transactions initiated would be logged. I would be interested to see if there were any errors relating to transactions.
3) Also who is involved here. I see that its the QM agent that is throwing the FFST. But it doesnt say whom does it belong to. I mean which process. Do you know which process. Does it belong to any of your applications or does it belong to Weblogic, if it starts one(i am not sure of whether it does or not).
4) How many processes are involved.
All this may not really lead us to the solution, but would narrow things down.
Cheers
Kumar |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Feb 19, 2004 2:43 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Feb 19, 2004 2:49 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
I don't think it is the same problem (AIX & Tuxedo vs my client's Solaris & MQ XA client).
More info:
The WebLogic apps are running on a separate box (hence client mode). We are using the WebSphere MQ Extended Transactional Client to do the XA work (on the WebLogic box).
That WebLogic box has more than 25 domains with many nodes running.
I ran "dspmqtrn -m XXXXX" and got "There are no prepared transactions."
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Feb 19, 2004 3:03 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Agree it is not the same problem (I know there is a difference to WebLogic vs Tuxedo and AIX vs Solaris )
but the problem description said something about a rollback of a transaction and something about not adhering to the XA protocol,
these things might give a clue.
Also you mentioned the Weblogic part is part of a large domain, still sure nothing changed on that end maybe since last weekend?
Problems not always appear right away 
I hope you find the culprit soon!
Michael |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Feb 19, 2004 3:35 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I think this isn't the exact problem that Michael referenced. However, this problem does look like it is an xa protocol type of error. I'd suggest that you contact IBM support. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Thu Feb 19, 2004 5:26 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
It sure smells like there is some confused transactional state. And it isnt definitely the problem the link is referring to, since the stack trace is totally different.
That was precisely the reason i asked to check the logs(if there is anything like that) for the Transaction co-ordinator to see what ever happend to the transaction or any transaction for that matter.
Cheers
Kumar |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Feb 19, 2004 8:51 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Since these are DEV boxes, I'm sure things are ever changing. 
Not adhering to the "XA protocol" standard. This is probably a good idea to check out because my client got WMQ Extended Transactional Client when it was firsted released!!! And you know what they say about v1.0 software. 
I think it is time to contact IBM.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
