|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Pub/Sub broker not running |
« View previous topic :: View next topic » |
Author |
Message
|
jarun111 |
Posted: Tue Aug 30, 2005 5:43 am Post subject: Pub/Sub broker not running |
|
|
Acolyte
Joined: 19 Apr 2004 Posts: 70
|
Hi,
We have a MAOC pub/sub pac along with MQ5.3 CSD06 Queue manager. Everything was working fine till 2 days back. All of a sudden pub/sub broker failed and is not getting restarted. Error log mentions. Any help would be greatly appreciated.
Thanks
=======================================
----- amqxfdcx.c : 722 --------------------------------------------------------
08/29/05 06:41:22
AMQ5878: WebSphere MQ Publish/Subscribe broker recovery failure detected.
EXPLANATION:
An earlier problem has occurred with the broker, and either a stream has been
restarted or the broker has been restarted. The restarted stream or broker has
detected that the previous instance of the stream or broker did not clean up
successfully and the restart will fail.
ACTION:
Investigate the cause of the failure that caused a stream or broker restart to
be necessary, and why the broker or stream was unable to clean up its resources
following the failure. When the broker processes with a non trusted routing
exit (RoutingExitConnectType=STANDARD), the broker runs in a mode where it is
more tolerant of unexpected failures and it is likely that the restart will
succeed after a short delay. In the case of a stream restart, the broker will
normally periodically retry the failing restart. In the case of a broker
restart, it will be necessary to manually retry the broker restart after a
short delay. When the broker processes without a routing exit, or with a
trusted routine exit (RoutingExitConnectType=FASTPATH), the broker runs in a
mode where it is less tolerant of unexpected failures and a queue manager
restart will be necessary to resolve this problem. When the broker is running
in this mode, it is important that the broker processes are not subjected to
unnecessary asynchronous interrupts, for example, kill. If the problem
persists, contact your IBM service representative.
======================================= |
|
Back to top |
|
 |
wschutz |
Posted: Tue Aug 30, 2005 6:01 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Well.... first, I'd sugggest getting to a current level of MQ v5.3 CSD's (like 9 or 10) and forgetting about Ma0c.
Are you running with a routingexit defined? and what platfrom? ( I assume there are no interesintg messages in the log from prior to 2 days ago related to the broker?) _________________ -wayne |
|
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
|
|
|
|