| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster Sender not Starting |
« View previous topic :: View next topic » |
| Author |
Message
|
| jondele |
 Posted: Tue Nov 18, 2008 2:54 pm Post subject: Cluster Sender not Starting |
 |
|
Newbie
Joined: 18 Nov 2008
Posts: 3
|
I have a cluster sender channel which is not starting when a message is put into a queue.
It was working before, what do i need to check to have the channel triggered?
I am running
Windows 2003 server
MQ 6.0.2.3
also,
i cant find the messages on any queue on the FR, so this leads me to believe its stuck somewhere. is there a xtmitq that holds these messages prior to hitting the Clustrsndr? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Nov 18, 2008 3:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The xmitq is SYSTEM.CLUSTER.TRANSMIT.QUEUE
If you have a problem with the channel, try checking its status and starting it manually (mqsc). Even though the channel does not have a local definition you can start it manually. If the message still does not move and the channel is in error you can check the logs on both sides. You should find there what is wrong. Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jondele |
| Posted: Tue Nov 18, 2008 4:19 pm Post subject: |
|
|
Newbie
Joined: 18 Nov 2008
Posts: 3
|
| I have been starting it manually the whole day. what do i need to check for in that queue? it exists and us allowed, put and get. non persistent. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Nov 18, 2008 5:23 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| jondele wrote: |
| I have been starting it manually the whole day. what do i need to check for in that queue? it exists and us allowed, put and get. non persistent. |
What do you see when you do a DIS CHS(*) on the QMgr where the cluster sender channel is defined?. The cluster sender channel should be either RUNNING or INACTIVE. If you have other than these, i.e., retrying or binding...then there is some problem with your channel definition or check for the destination QMgr hostname(ip) etc. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 19, 2008 1:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
A manually defined cluster sender shouldn't be triggered & shouldn't need to be. As previously posted, if it's not RUNNING or INACTIVE check the channel log to see what's up.
If the channel's ok but there are no messages on the target FR, make sure the putting app is either a) specifying the target queue manager name correctly or better still b) not specifying a queue manager & BIND_NOT_FIXED.
From here there's a whole discussion about the "stuck" messages being addressed to a non-responsive (or non-existant) queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jondele |
| Posted: Wed Nov 19, 2008 10:33 am Post subject: |
|
|
Newbie
Joined: 18 Nov 2008
Posts: 3
|
so i looked deeper into this, all my messages are getting stuck in SYSTEM.CLUSTER.TRANSMIT.QUEUE
channel is fine once i start it, it flows through
i did notice in the logs, im getting a lot of crashes.
could this be something i need to worry about as well?
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:05:35 - Process(3288.3) User(TSGMQP01) Program(amqzmuc0.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806824. This message is
issued in association with other messages.
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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:05:35 - Process(3288.3) User(TSGMQP01) Program(amqzmuc0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CRNSUBP3.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3288.
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.
----- amqxfdcp.c : 804 --------------------------------------------------------
11/17/2008 00:05:48 - Process(3636.1467) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Rc=112 from
SetEndOfFile)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The 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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:05:48 - Process(3636.1467) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CRNSUBP3.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3636.
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.
----- amqxfdcp.c : 804 --------------------------------------------------------
11/17/2008 00:11:12 - Process(3636.1468) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Rc=112 from
SetEndOfFile)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The 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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:11:12 - Process(3636.1468) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CRNSUBP3.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3636.
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.
----- amqxfdcp.c : 804 --------------------------------------------------------
11/17/2008 00:29:06 - Process(3636.1509) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Rc=112 from
SetEndOfFile)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The 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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:29:06 - Process(3636.1509) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CRNSUBP3.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3636.
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.
----- amqxfdcp.c : 804 --------------------------------------------------------
11/17/2008 00:29:06 - Process(3636.1510) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Rc=112 from
SetEndOfFile)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The 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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/17/2008 00:29:06 - Process(3636.1510) User(TSGMQP01) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager CRNSUBP3.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3636.
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.
----- amqxfdcp.c : 804 --------------------------------------------------------
11/18/2008 22:13:45 - Process(3808. User(TSGMQP01) Program(amqzxma0.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20805301. This message is
issued in association with other messages.
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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/18/2008 22:13:45 - Process(3808. User(TSGMQP01) Program(amqzxma0.exe)
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 3808.
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.
----- amqxfdcp.c : 810 --------------------------------------------------------
11/18/2008 22:14:45 - Process(3808. User(TSGMQP01) Program(amqzxma0.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806105. This message is
issued in association with other messages.
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.
----- amqxfdcp.c : 766 --------------------------------------------------------
11/18/2008 22:14:45 - Process(3808. User(TSGMQP01) Program(amqzxma0.exe)
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 3808.
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. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Nov 19, 2008 12:02 pm Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
The above statement is saying something with OS to do. did you guys change anything to OS when this error occured?. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 19, 2008 12:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jondele wrote: |
i did notice in the logs, im getting a lot of crashes.
could this be something i need to worry about as well?
|
No, the software's designed to crash repeatedly....! 
Check and see if there are any FDC files associated with these errors (there should be, but one of the failing process is concerned with producing them!). If there are, look at the Probe ID in the file, Google it, see if there's any relevant information.
Also check for recent changes to the platform, noteably security or service changes.
In extremis, it's PMR time. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
