| Author |
Message
|
| dc01bb |
 Posted: Mon Feb 11, 2013 9:33 am Post subject: How to find rogue application filling up logs |
 |
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
We have a rogue application that is fiing up LOGS on one of our AIX queue managers which we can see getting killed via AMQ7469: Transactions rolled back to release log space.
We've surveyed the usual suspects and no one is reporting receiving MQRC 2003s. I ran an API trace and didn't find any instances of the 007d1 that would be a 2003.
Is anyone aware of a technique that has been successfully used to figure out who is causing this?
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 11, 2013 9:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| have you looked at channels? |
|
| Back to top |
|
|
| dc01bb |
| Posted: Mon Feb 11, 2013 9:58 am Post subject: |
|
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
Wouldn't channels show up in the API trace?
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| dc01bb |
| Posted: Mon Feb 11, 2013 10:00 am Post subject: |
|
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
There are now outbound channels from the queue manager that are in retrying state, and neither are there channel stop/start messages in the logs that correspond with these times. And they come at varying intervals not the intervals that correspond with our typicall long and short retries.
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 11, 2013 10:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
might not be outbound channels.
long running transactions might not be doing anything that would cause the 2003 to be reported immediately.
i.e. an app that has done a bunch of work, failed to commit, and then gone to sleep before mqdisc/mqcmit might not receive a 2003 because it hasn't tried to do anything else with the queue handle or qmgr handle. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 11, 2013 10:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| dc01bb wrote: |
| There are now outbound channels from the queue manager that are in retrying state... |
Not a surprise. Message channel agents are much like other applications. Once logs are full, message channel agents cannot continue to get/put in syncpoint.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dc01bb |
| Posted: Mon Feb 11, 2013 10:17 am Post subject: |
|
|
Novice
Joined: 25 Oct 2001
Posts: 17
Location: Bruce Baxter
|
Sorry. I had a typo. where you quote ''there are NOW", it should have been NO.
But' I'm stil thinking I would have picked off a 7D1 status in my traces that I did.
_________________
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| Andyh |
| Posted: Mon Feb 11, 2013 10:47 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
You can use the UOWLOGDA/UOWLOGTI fields of the runmqsc DIS CONN
output to identify long running transactions.
MQ V7.5 also allows dspmqtrn to show active (vs indoubt) transactions. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 11, 2013 10:54 am Post subject: Re: How to find rogue application filling up logs |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| dc01bb wrote: |
| We have a rogue application that is fiing up LOGS on one of our AIX queue managers which we can see getting killed via AMQ7469: Transactions rolled back to release log space. |
This presumes that you have allocated sufficient logs to handle the usual workload, plus peak workload.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 11, 2013 10:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| but the api trace might show you enough information about which transaction is in involved to let you find out which connection is involved which might show you enough to find out what process is involved? |
|
| Back to top |
|
|
|
|
