|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
runmqchl hanging even after stopping the channel - Urgent |
« View previous topic :: View next topic » |
Author |
Message
|
Jeeva |
Posted: Mon Apr 04, 2005 5:28 am Post subject: runmqchl hanging even after stopping the channel - Urgent |
|
|
Novice
Joined: 16 Feb 2005 Posts: 12 Location: India
|
Hi All,
We have a server - Requester channel and channel exit on the requester channel which modifies all my incoming messages and sent it to the local queue of the destination queue manager. Server channel in source queue manager and Requester channel in Destination queue manager.
Channel exit has one global variable loaded with some values in its initialization and the variable is used to modify all the incoming messages. When the channel exit terminates it frees the global variable buffer(pointer) as well as local pointers.
I am starting my server channel and then my requester channel. Now I am able to see the runmqchl running for my channel for destination queue manager.
$ ps -ef | grep runmqchl
mqm 17019 10569 0 12:50:09 ? 0:00 /opt/mqm/bin/runmqchl -c <channel name> -m <QM name>
Stopping both the channels and the status showed as "STOPPED" but runmqchl is still running.
04/04/05 12:54:02 PM
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 : 673 --------------------------------------------------------
04/04/05 12:54:02 PM
AMQ6184: An internal WebSphere MQ error has occurred on queue manager <Destination QM>.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been
called. The failing process is process 17019.
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 : 707 --------------------------------------------------------
The failing process id is nothing but runmqchl process id. This error log from /var/mqm/errors.
When i start again i am getting one more runmqchl for the same channel.
$ ps -ef | grep runmqchl
mqm 19822 10569 0 12:57:24 ? 0:00 /opt/mqm/bin/runmqchl -c <channel name> -m <Destination QM>
mqm 17019 10569 0 12:50:09 ? 0:00 /opt/mqm/bin/runmqchl -c <channel name> -m <Destination QM>
Channel status is RUNNING and I am able to send message successfully and the channel exit process it successfully and sends it to the local queue of the destination.
Now If I stop the channels , Requester channel goes in to STOPPING status..
error log is
04/04/05 01:00:19 PM
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 : 673 --------------------------------------------------------
04/04/05 01:00:19 PM
AMQ6184: An internal WebSphere MQ error has occurred on queue manager <Destination QM>.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has been
called. The failing process is process 19822.
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 : 707 --------------------------------------------------------
If anyone faced simillar kind of issue, throw some light..
Abinav |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Apr 04, 2005 5:53 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
The usual thing to do in this sort of situation is to remove references to your channel exit from all the channels involved, then run the test again. That way, you eliminate the possibility that the problem is caused by your exit. |
|
Back to top |
|
 |
Jeeva |
Posted: Mon Apr 04, 2005 6:23 am Post subject: |
|
|
Novice
Joined: 16 Feb 2005 Posts: 12 Location: India
|
Hi,
I did that and it is working fine. I am sure that the channel exit causing it.
I want to know what kind of errors in channel exit may cause this type of error. Like inproper handling of pointers etc., I have freed all the pointers in the channel exit termination.
Jeeeva |
|
Back to top |
|
 |
Jeeva |
Posted: Mon Apr 04, 2005 8:03 am Post subject: |
|
|
Novice
Joined: 16 Feb 2005 Posts: 12 Location: India
|
Resolved..
Issue raised due to improrper Pointer hadling in one place..
thanks for ur comments guys..
Jeeeva |
|
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
|
|
|
|