| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ6209 & FDC Generated. |
« View previous topic :: View next topic » |
| Author |
Message
|
| aboggis |
 Posted: Thu Sep 11, 2003 9:20 am Post subject: AMQ6209 & FDC Generated. |
 |
|
Centurion
Joined: 18 Dec 2001
Posts: 105
Location: Auburn, California
|
I am getting some queue manager failures locally with FDC files generated:
| Code: |
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Wednesday September 10 15:24:25 PDT 2003 |
| Host Name :- vdpsusptar01 (SunOS 5.8) |
| PIDS :- 5765B75 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Dec 11 2002 |
| CMVC level :- p520-CSD06G |
| Build Type :- IKAP - (Production) |
| UserID :- 00001002 (aboggis) |
| Program Name :- runmqlsr_nd |
| Process :- 00026194 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (1) has |
| been received and ignored. |
| Arith1 :- 1 1 |
| Arith2 :- 26194 6652 |
| |
+-----------------------------------------------------------------------------+
|
All the qmgr processes appear to still be running, but I am getting 2059 error when trying to connect from a client, so I will have to restart the qmgr anyway.
My theory is that since this is from 'runmqlsr' that it was generated when I logged off from my terminal session. Now I started the listener with the '&', which according to the MQ docs says that the process will ignore signals when the user's session is terminated.
The only other errors I have are in the queue manager's own log files, stating that a channel to another remote qmgr has ended abnormally because the host is unavailable. Interestingly, this queue manager is also showing the same errors and generating the same sort of FDC files...
tonyB. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Sep 11, 2003 9:57 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Tony, me 'ole mate,
It's not just the '&' you need. That will put the process in the background, but it's still connected to your logon ID. Use the 'nohup' command to start the listener as well as the '&'. That will make it ignore the SIGHUP when you logoff.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jeevankc |
| Posted: Mon Nov 14, 2005 8:28 pm Post subject: How to solve MQ errors 2009 and 2059 |
|
|
Newbie
Joined: 14 Nov 2005
Posts: 1
|
Hi, I have installed MQ version 6 on AIX 5.3 .
We have done the following steps to configure MQ.
1. crtmqm -q QueueManagerName
2. strmqm QueueManagerName
3. Defined all the appropriate Channels
4. started the runmqsc window and started all the channels
START Channel(ChannelName)
5. Started the Listeners in the backgroud like
runmqlsr -m QueueManagerName -p portNo -t tcp &
6. I could able to ping the channels which i defined like
PING CHANNEL(ChannelName)
7. I could able to see the Channel Status
DISPLAY CHS('ChannelName')
8. I could able to see the status of Local Queue
DISPLAY QLOCAL('Xmit Queue Name')
9. Set the Authorization for roo user like
setmqaut -m QManagerName -t qmgr -p root +dsp +connect
setmqaut -m QManagerName -t q -n LocalQueueName -p root +dsp +get +put +browse
setmqaut -m QManagerName -t q -n RemoteQueue -p root +dsp +get +put +browse
setmqaut -m QManagerName -t qmgr -p root +all inq
After doing all the above steps when i try to run sample C programme which is there in the /usr/mqm/samp/bin directory
amqsput RemoteQueueName
It will ask to type something and after entering twice the message will put into the RemoteQueue. And in the Host side they could able to see the message.
But when we try running a Java programme which does the same thing we are getting the following errors....
11/14/05 18:41:27 - Process(352444.2) User(mqm) Program(runmqlsr_nd)
AMQ6209: An unexpected asynchronous signal (1 : SIGHUP) has been received and
ignored.
EXPLANATION:
Process 0 received an unexpected asynchronous signal and ignored it. This has
not caused an error but the source of the signal should be determined as it is
likely that the signal has been generated externally to WebSphere MQ.
ACTION:
Determine the source of the signal and prevent it from re-occurring.
----- amqxfdcx.c : 771 --------------------------------------------------------
11/14/05 18:41:27 - Process(352444.2) User(mqm) Program(runmqlsr_nd)
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 352444.
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 : 816 --------------------------------------------------------
Appreciate if some one help me on this.
Thanx in advance.
jee |
|
| Back to top |
|
|
| punnam |
| Posted: Tue Nov 15, 2005 12:22 pm Post subject: |
|
|
Novice
Joined: 12 Apr 2005
Posts: 19
|
5. Started the Listeners in the backgroud like
runmqlsr -m QueueManagerName -p portNo -t tcp &
When you are starting listener you should use nohup,so that the process will not end after you logged off .I am not sure it fixes the problem or not
nohup runmqlsr -m QueueManagerName -p portNo -t tcp & |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 15, 2005 5:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| punnam wrote: |
5. Started the Listeners in the backgroud like
runmqlsr -m QueueManagerName -p portNo -t tcp &
When you are starting listener you should use nohup,so that the process will not end after you logged off .I am not sure it fixes the problem or not
nohup runmqlsr -m QueueManagerName -p portNo -t tcp & |
I thought this would only be pertinent for linux.
We run MQ 5.3 on AIX and Solaris and do not use nohup.
The process survives fine when you logoff if you put it into background (&).
 |
|
| 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
|
|
|
|
