Stefan,
MQSeries will write the AMQ7604 message when an active resource manager (RM) falls over in some way. We try to reestablish communications with the RM at startup and whenever an application tries to involve it in a new unit of work, and if our xa_open call succeeds we should print the AMQ7625. Since the retry is automatic in the sense that it happens in response to new application requests, I would guess that there must be some error returned from DB2's xa_open call. I think a trace of an application trying coordinate DB2 once it comes up would be most helpful. If you wish, you can send me one off the list.
Justin T. Fries
MQSeries Support
Raleigh, North Carolina
Email: [EMAIL PROTECTED]
| Stefan Sievert <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]> 06/12/2002 20:12
|
To: [EMAIL PROTECTED] cc: Subject: MQ/DB2 XA - re-establishing contact after DB2 restart |
Hi everyone,
if you have an MQ and a DB2 that are married through XA and the DB2 becomes
unavailable, what causes the queue manager to re-establish the connection to
DB2?
The docs say it is an automatic process with no intervention needed, but it
looks like it doesn't happen automagically in our environment (AIX 4.3.3,
MQ5.2, DB2 7.1 FixPac 3). We never see the message AMQ7625 in our
AMQERR01.logs, which is what I would expect to happen.
What we see is message AMQ7604, which is OK because DB2 was brought down.
But it looks like the connection is not re-established once DB2 is
restarted.
Any takers on this? Input of any form is much appreciated!
Stefan
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
