| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ6109 and AMQ6183 |
« View previous topic :: View next topic » |
| Author |
Message
|
| ryan76 |
 Posted: Thu Oct 20, 2005 12:23 am Post subject: AMQ6109 and AMQ6183 |
 |
|
Newbie
Joined: 20 Oct 2005
Posts: 3
|
in mq log(/var/mqm/error) I always find following error:
----- amqxfdcx.c : 728 --------------------------------------------------------
10/19/05 21:23:03
AMQ6109: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been
called.
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.
----- amqxfdcx.c : 688 --------------------------------------------------------
10/19/05 21:23:04
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been
called. The failing process is process 2900150.
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.
----- amqxfdcx.c : 728 --------------------------------------------------------
FDC:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday October 20 13:38:57 BEIST 2005 |
| Host Name :- KF_DB (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- May 12 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000218 (db2irun) |
| Program Name :- runmqlsr_nd |
| Process :- 02650262 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1 1 |
| Comment1 :- SIGHUP |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST
my environment:
AIX V5.2.0
MQ V5.2 CSD10
I am not able to resolve it. Please help me |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Oct 20, 2005 1:02 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
looks like you are on MQ 5.3 CSD10, not 5.2
Well, i assume you searched IBM for possible ptf, if not hit found i recommend to follow the hint in the error:
| Quote: |
Contact your IBM support
center |
maybe csd11 could help.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| ryan76 |
| Posted: Thu Oct 20, 2005 1:11 am Post subject: |
|
|
Newbie
Joined: 20 Oct 2005
Posts: 3
|
|
| Back to top |
|
|
| harry_hotdog |
| Posted: Thu Oct 20, 2005 1:37 am Post subject: |
|
|
Novice
Joined: 19 Oct 2005
Posts: 10
Location: England
|
I don' think so.
The signal in the link is SIGTERM, and your FFST has signal SIGHUP.
I think your FFST is caused when you start the listener to run
asynchronously, and then log off the terminal where you started it. This
will cause a SIGHUP signal to be sent to the process. The FFST notifies
you that the signal has been sent, and tells you that runmqlsr has ignored
it.
If the FFST bothers you, you can fix it by:
1. Leave the console where you start the listener logged in
2. Run the listener in the foreground
3. use nohup to start the listener,
e.g
nohup runmqlsr -m QM -p 1414 & > nohup.out 2>&1 |
|
| Back to top |
|
|
| ryan76 |
| Posted: Thu Oct 20, 2005 11:58 pm Post subject: |
|
|
Newbie
Joined: 20 Oct 2005
Posts: 3
|
harry_hotdog thank u
you are right.
although I installed the csd11 the problem still on
this is my script for runing listener:
nohup runmqlsr -t tcp -p 1417 -m QMGA &
Do you think there is any problems about the script ? |
|
| 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
|
|
|
|
