Posted: Thu Nov 20, 2008 5:33 pm Post subject: Probe Id: AT048005 i.e AMQ6125: An internal WebSphere ...
Newbie
Joined: 20 Nov 2008 Posts: 1
Hi All,
I have a problem with MQ throwing exception severial times a day with FDC files that shown below.
I saw in the web that this is an issue that will be fixed if we install CSD3. Is that right?
What is the implication to my MQ functionality if i did not fix it?
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday September 22 16:48:17 SGT 2008 |
| Host Name :- xxxx (SunOS 5. |
| PIDS :- 5724B4103 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- AT048005 |
| Application Name :- MQM |
| Component :- atxCommit |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00001001 (mqm) |
| Program Name :- amqzlaa0_nd |
| Process :- 00000297 |
| Thread :- 00003495 |
| QueueManager :- xxxx |
| 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 |
| Arith1 :- 278921216 10a00000 |
| Arith2 :- 1073741824 40000000 |
| |
+-----------------------------------------------------------------------------+
Posted: Fri Nov 21, 2008 1:16 am Post subject: Re: Probe Id: AT048005 i.e AMQ6125: An internal WebSphere ..
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
sheristopher wrote:
saw in the web that this is an issue that will be fixed if we install CSD3. Is that right?
If you're going to apply a fix apply the latest CSD (which includes the fixes for CSD 3). But fixing v5.3 is putting lipstick on a pig - it's still out of support and shouldn't be used.
sheristopher wrote:
What is the implication to my MQ functionality if i did not fix it?
Without looking up the specific error I'd say a) it's going to keep failing and b) you're probably going to keep having issues with committing transactions.
Mind you, if you're running v5.3 without even CSD3 applied it's a miracle it's actually providing any functionality at all. _________________ Honesty is the best policy.
Insanity is the best defence.
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