| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Probe Id AL004011 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Al Pacino |
 Posted: Thu Apr 14, 2011 12:02 am Post subject: Probe Id AL004011 |
 |
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
Hi there,
We started to face an issue one our Unix system with MQ. We are running MQ p701-104-110114 on AIX 6.1 64-bit . This is a highly available environment where logs are shared on a separate SAN.
We have checked , space , permission, network , we can't seem to figure the cause.
Please advice
The queue manager would fail and causes the node to switch over .. here is the FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu April 14 2011 01:00:25 SAUST |
| UTC Time :- 1302732025.356074 |
| UTC Time Offset :- 180 (SAUST) |
| Host Name :- mqbprddb2 |
| Operating System :- AIX 6.1 |
| PIDS :- 5724H7221 |
| LVLS :- 7.0.1.4 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- AL004011 |
| Application Name :- MQM |
| Component :- almLogIt |
| SCCS Info :- lib/lqm/amqalmw0.c, 1.42.1.1 |
| Line Number :- 603 |
| Build Date :- Jan 14 2011 |
| CMVC level :- p701-104-110114 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 205 (mqm) |
| Real UserID :- 205 (mqm) |
| Program Name :- amqzlaa0_nd |
| Addressing mode :- 64-bit |
| Process :- 9633946 |
| Thread :- 13188 |
| QueueManager :- WMQ |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 57967 |
| ConnId(2) QM :- 13456 |
| Last HQC :- 2.5.5-4939672 |
| Last HSHMEMB :- 1.2.2-311128 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_LOG_DAMAGED |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806706) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545285894 (0x20806706) |
| |
+-----------------------------------------------------------------------------+
[edit] deleted stack info [/edit]
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them."
Last edited by Al Pacino on Thu Apr 14, 2011 1:00 am; edited 1 time in total |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Apr 14, 2011 12:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Al, please remove the stack trace from your post, it's of little or no use except to the eggheads at Hursley, and makes the post hard to read.
There is a hit on IBM for that Probe ID, and the cause was supposed to be fixed in FixPack 7.0.1.4, so I suggest that you examine the usage profile for the queue manager, i.e. is it now under more stress that previously, and open a PMR.
_________________
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 |
|
|
| mqjeff |
| Posted: Thu Apr 14, 2011 1:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Aside from the previously mentioned APAR, there is
| Minor Errorcode :- hrcE_LOG_DAMAGED |
which is pretty clear? |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 14, 2011 1:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqjeff wrote: |
Aside from the previously mentioned APAR, there is
| Minor Errorcode :- hrcE_LOG_DAMAGED |
which is pretty clear? |
I've seen that reported in cases where there is very high IO, and a delayed OS response to an access request is considered 'bad' and interpreted as a damaged log. Subsequent restart has been OK, and no report of corrupt/unavailable/damaged logs.
_________________
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 |
|
|
| Al Pacino |
| Posted: Thu Apr 14, 2011 2:29 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
| mqjeff wrote: |
Aside from the previously mentioned APAR, there is
| Minor Errorcode :- hrcE_LOG_DAMAGED |
which is pretty clear? |
The error sounds clear , however, there is no damaged log or queue once we started to look. When we reboot , things start running fine and MQ has no problem starting. IBM did provide a fix which is the latest out there , however, even after applying the fix , the issue still reoccur. Something to do with the I/O as exerk mention but we don't seem to figure it out. Not much on google either regarding this prob Id.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Apr 14, 2011 2:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| So if it only occurs under heavy use of the log files, and the log files are kept on SAN, it sounds like you might want to tune your SAN to meet the needs during high load.. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
