Tim Zielke
2014-04-04 13:22:44 UTC
Hello,
We have noticed in our distributed MQ queue manager logs (i.e. AMQERR01.LOG) that a few of our queue managers are reporting the following messages around 1-2 times a day.
AMQ7469: Transactions rolled back to release log space.
AMQ7486: Transaction 0.43630562 was preventing log space from being released.
AMQ7487: Application java was preventing log space from being released.
We have the file system for our transaction log very large on the queue managers (in the 6 gig range), so we feel pretty sure this is an application with a runaway transaction or not behaving properly. We implemented a script to capture ps information every 10 minutes (this is on Red Hat Linux) so we could tie the pid number being reported in the AMQ7487 message to the specific offending application. For the first 5 occurrences, it was always application A, so we thought we had the culprit.
However, today another application B was reported as being the one with the long running transaction and being rolled back. But I do see the previously offending application A was running at the same time and had been running for 20 hours. Application B had been running for an hour when it's transaction was rolled back. Only application B was reported as having it's transaction rolled back to free log space for this latest occurrence of the issue.
I was curious if anyone on this LISTSERV knows. Is it possible that application A was the main culprit for filling the transaction log, but MQ rolled back application B because it had a somewhat sizeable transaction, too? Or in the case where the transaction log becomes full and MQ rolls back a transaction, would it always target the application with the largest transaction?
Thanks,
Tim
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
We have noticed in our distributed MQ queue manager logs (i.e. AMQERR01.LOG) that a few of our queue managers are reporting the following messages around 1-2 times a day.
AMQ7469: Transactions rolled back to release log space.
AMQ7486: Transaction 0.43630562 was preventing log space from being released.
AMQ7487: Application java was preventing log space from being released.
We have the file system for our transaction log very large on the queue managers (in the 6 gig range), so we feel pretty sure this is an application with a runaway transaction or not behaving properly. We implemented a script to capture ps information every 10 minutes (this is on Red Hat Linux) so we could tie the pid number being reported in the AMQ7487 message to the specific offending application. For the first 5 occurrences, it was always application A, so we thought we had the culprit.
However, today another application B was reported as being the one with the long running transaction and being rolled back. But I do see the previously offending application A was running at the same time and had been running for 20 hours. Application B had been running for an hour when it's transaction was rolled back. Only application B was reported as having it's transaction rolled back to free log space for this latest occurrence of the issue.
I was curious if anyone on this LISTSERV knows. Is it possible that application A was the main culprit for filling the transaction log, but MQ rolled back application B because it had a somewhat sizeable transaction, too? Or in the case where the transaction log becomes full and MQ rolls back a transaction, would it always target the application with the largest transaction?
Thanks,
Tim
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html