MQSeries.net :: View topic

vineet.rawat · Posted: Tue Dec 27, 2005 4:11 am Post subject:

I have Webphere MQ 5.3 on the machine.I have installed Fix 11 on my machine to enable publish Subscribe model.Before Fix 11 Fix 8 was installed on the machine which was then uninstalled to install fix 11.
After 2 day of correct working broker has started giving following error...

----- amqxfdcp.c : 665 --------------------------------------------------------
12/13/2005 08:02:28
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.
----- amqxfdcp.c : 631 --------------------------------------------------------
12/13/2005 08:02:29
AMQ6184: An internal WebSphere MQ error has occurred on queue manager METPTAQM.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4928.
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 : 665 --------------------------------------------------------
12/13/2005 08:02:29
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.
----- amqxfdcp.c : 631 --------------------------------------------------------
12/13/2005 08:02:29
AMQ6184: An internal WebSphere MQ error has occurred on queue manager METPTAQM.

EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4928.
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 : 665 --------------------------------------------------------
12/13/2005 08:02:29
AMQ5878: WebSphere MQ Publish/Subscribe broker recovery failure detected.