| Author |
Message
|
| ChrisW |
 Posted: Fri May 25, 2007 1:53 am Post subject: AMQ7467/AMQ7468 Frequency |
 |
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
Hi,
I have a development Queue Manager (Windows 5.3 CSD 11) which has AMQ7467/AMQ7468 messages in the error log every 13 seconds (thats the oldest log messages). In consequence, the 3 files last about 90 mins. As I understand it, these come out at every checkpoint (10000 operations?). Not much going through message wise. I have left a trace running for a while - by far the largest file is from dllhost.exe. We have Biztalk Adapter for MQ (2004) on here so I assume that this is the culprit.
Anyone any ideas on this?
Cheers,
Chris. |
|
| Back to top |
|
 |
| dgolding |
| Posted: Fri May 25, 2007 4:36 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
|
| Back to top |
|
|
| ChrisW |
| Posted: Fri May 25, 2007 8:04 am Post subject: |
|
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
| Thanks for that. Anyone any idea what its doing? I guess continually polling the queue and issuing loads of begin transactions, commits, and end transctions? Certainly no (or not many) messages for it. So quality programming from Microsoft! |
|
| Back to top |
|
|
| dgolding |
| Posted: Fri May 25, 2007 8:19 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| To be honest, no, I've never used the product, and actually I thought it was every 1000 operations that an entry was written to the AMQERR01.LOG file, but I couldn't swear to it..... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 25, 2007 10:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Guys you need to get out more and work more with Linear Logging.
a) You really don't want to suppress those messages as they are used when you look at archiving the log files...
b) a number of additional events can trigger such a message in the log. I have seen those 2 messages immediately after a channel tcp/ip error being logged...
So if you cycle so fast:
Are you doing a lot of work with persistent messages during this interval? If not do you have a lot of communications errors in the logs?
And finally have you sized adequately your log files?
Remember to change the log file size you must recreate the qmgr...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dgolding |
| Posted: Fri May 25, 2007 12:59 pm Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| Actually, when ChrisW said "3 logs" I thought he was worried about his AMQERR0N.LOG and the issue was he only had 90 minutes of info for the three of them |
|
| Back to top |
|
|
| ChrisW |
| Posted: Fri May 25, 2007 9:42 pm Post subject: |
|
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
Yes thats right!
We are linear logging and have no worries there. Record Images and log archiving all set up. But at present they are only putting through about 100 messages a day, there are no channel errors, in fact hardly anything else in the AMQERRnn logs except these messages. As we will use Patrol to alert for any other messages then no real problems and it would be worth increasing their size so we don't lose so much history.
I suppose my question really is about the Biztalk adapter and what the hell is it doing all the time to cause lots of "transaction logging" when processing nothing (and thus all the messages). And maybe someone knows how to change its behaviour as our Biztalk people have no idea. However, in terms of absolute CPU consumption it doesn't seem too bad so maybe I am worrying too much.
Otherwise, even our busiest production Windows Queue Manager using linear logging uses about 1 AMQERRnn file a day, not one every 30 mins. |
|
| Back to top |
|
|
| dgolding |
| Posted: Sat May 26, 2007 12:32 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| fjb_sapers suggestion of increasing your transaction log size is a good one, as you should do log switching less often, hence less messages. |
|
| Back to top |
|
|
| ChrisW |
| Posted: Sat May 26, 2007 4:28 am Post subject: |
|
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
The transaction logs are already at maximum size and the use of them is not the problem here. In fact its not really using many at all. I think probably whats happening is Biztalk is doing lots of begin transactions, attempting a get (2033) and end transactions, contributing to the checkpoint "counter" but not actually writing to the transaction logs very much as there is rarely a message there.
Sounds like the best bet is to simply increase the sizes of the error logs and put up with them, unless I can spot something in Biztalk to change.
Thanks for all your comments. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 26, 2007 7:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Biztalk adapter to MQ should be a supported configuration.
You should be able to raise a service request with either M$ or IBM or both.
Hope you get it fixed soon.
Let us know what the cause and resolution turned out to be.
Thanks
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
