| Author |
Message
|
| pettitma |
 Posted: Wed Oct 19, 2005 8:28 am Post subject: Primary/Secondary log files |
 |
|
Novice
Joined: 26 Apr 2005
Posts: 18
|
Hi,
We've created a qmgr with 40 Prim and 20 Secondary linear logs, logfilepages of 256kb. Everything is persistant. Our average message size is just 2k (and nothing bigger than 4k)
During testing we sent approx 150,000 msgs to the qmgr (actually via Biztalk) but after approx 110,000 were sent we started to get the 'Transactions rolled back to release log space' error (msgs were building up within MQ)
I can perform the same task on a test env though and stack millions up in the queues with no problems.
What am I missing here? (no witty comments to that one please  )
MQ 5.3 CSD07 Windows AS 2000 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 19, 2005 8:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe the configuration in BizTalk is different for your test environment, and is putting all 150,000 messages in the same transaction.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pettitma |
| Posted: Wed Oct 19, 2005 9:14 am Post subject: |
|
|
Novice
Joined: 26 Apr 2005
Posts: 18
|
| Hi Jeff, many thanks for the quick reply. I've had a chat with the biztalk chaps and what they apparently do is batch the messages into transactions of 100 messages (still only 2/3k a msg). Could this still be the problem you think? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 19, 2005 9:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It may be something else entirely that is hogging your transaction log space, and affecting you but not it...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Oct 19, 2005 10:16 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
just a guess... what's your uncommitted message count on your new queuemanager? (10000 is default) and what is on your test queuemanager?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| pettitma |
| Posted: Thu Oct 20, 2005 1:05 am Post subject: |
|
|
Novice
Joined: 26 Apr 2005
Posts: 18
|
Hi Michael,
Well, assuming this is the same thing.. looking at the qmgr properties, the Maximum Uncommitted Messages is set to 10,000.
However, not noticed this before - when creating a new qmgr, you get to set the Max Uncommitted Msgs value , it's default is always 1,000, but even if you set it to this, looking at the qmgrs properties when you bring it up is set to 10,000. odd.
Anyway, it's set to 10,000 on all qmgrs by the look of it.
cheers,
Matt |
|
| Back to top |
|
|
| tkane |
| Posted: Thu Oct 20, 2005 10:29 am Post subject: |
|
|
Voyager
Joined: 23 Dec 2002
Posts: 82
Location: Kansas City
|
As I understand it: when AMQ7469 is issued, something is rolled back. And the application gets error code: MQRC_BACKED_OUT.
I verified this by taking amqsput0.c and changing it pmo_syncpoint and putting a MQCMIT right before the MQCLOSE.
I put 3 messages and then waited while my queue manager rolled through 60+ 64mb logs. About an hour later I tried to put another message (still under the first syncpoint) and got MQRC_BACKED_OUT (2003) from the MQPUT and MQCMIT.
There's goodness and badness to the way this works. If you're an application and looking at all your return codes, you can detect this easily.
If you're an MQ Systems person with tons of queue managers and get alarms from your monitoring software for AMQ7469 you're probably going to have a fun time figuring out why this is happening.
Good Luck
Tom |
|
| Back to top |
|
|
|
|
