MQSeries.net :: View topic

bustacap · Posted: Tue Mar 20, 2007 6:49 am Post subject:

Hi there, I'm new to MQ and was just wondering if in doubt transactions will causes a queue manager to shut down automatically? See an excerpt of my error log below. Since there are many people who have access to this server, I'm not sure if the shut down command was entered manually by another administrator or if the queue manager shut down by itself.

-------------------------------------------------------------------------------
03/05/07 04:40:23
AMQ7605: The XA resource manager MQSeries has returned an unexpected return
code -3, when called for xa_commit.

EXPLANATION:
WebSphere MQ received an unexpected return code when calling XA resource
manager MQSeries at its xa_commit entry point. This indicates an internal
error, either within MQ or the resource manager.
ACTION:
Try to determine the source of the error. A trace of the failure could be used
to look at the XA flows between MQ and the resource manager. MQ has allocated
an RMId of 0 to this resource manager. This will be useful when isolating the
flows associated with the resource manager concerned. If the error occurs on an
xa_commit or xa_rollback request, the queue manager will not attempt to
redeliver the commit or rollback instruction for this transaction, until after
the queue manager has been restarted. The transaction indoubt is identified by
the following XID of
X'abc123hex'. If you think
that the error lies within the queue manager, contact your IBM support center.
Do not discard any information describing the problem until after the problem
has been resolved.
----- amqtmcma.c : 855 --------------------------------------------------------
03/05/07 04:40:24
AMQ7606: A transaction has been committed but one or more resource managers
have backed out.

EXPLANATION:
WebSphere MQ was processing the commit operation for a transaction involving
external resource managers. One or more of these resource managers failed to
obey the commit request and instead rolled back their updates. The outcome of
the transaction is now mixed and the resources owned by these resource managers
may now be out of synchronization. MQ will issue further messages to indicate
which resource managers failed to commit their updates.
ACTION:
The transaction with the mixed outcome is identified by the following XID of
X'abc123hex'. The messages
which identify the failing resource managers will also contain this same XID.
If the transaction has completed it won't be displayed by the dspmqtrn command
and all other transaction participants will have committed their updates. If
the transaction is displayed by the dspmqtrn command then there are some
participants still in prepared state. In order to preserve data integrity you
will need to perform recovery steps local to the failing resource managers.
----- amqtmfga.c : 353 --------------------------------------------------------
03/05/07 08:30:24
AMQ9542: Queue manager is ending.

EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.