MQSeries.net :: View topic

mrlazy · Posted: Tue May 22, 2007 3:52 am Post subject:

hi,
we have apps which use mq 5.2, pub-sub installed on one of our prod systems (win 2000). but very recently, i have upgraded mq 5.2 to mq 5.3 csd 12 , and got rid of the pub-sub product,since it comes along with the fix pack.

though it works fine intially, after some time, mq broker stops for some reason, and when i try to restart it, it's throwed messages below. could one of you mq experts tell me how to fix tihs issue?

there will be thousands of messages going across this queue manager on a daily basis. Search didn't return with any useful posts

05/21/2007 13:27:38
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.

ans also:

05/21/2007 13:27:38
AMQ5819: An WebSphere MQ Publish/Subscribe broker stream has ended abnormally.
EXPLANATION:
The broker stream (SYSTEM.BROKER.ADMIN.STREAM) has ended
abnormally for reason 0. The broker will attempt to restart the stream. If the
stream should repeatedly fail then the broker will progressively increase the
time between attempts to restart the stream.
ACTION:
Investigate why the problem occurred and take appropriate action to correct the
problem. If the problem persists, contact your IBM service representative.