Author |
Message
|
noles321 |
Posted: Tue Nov 30, 2004 1:07 pm Post subject: error log |
|
|
Apprentice
Joined: 15 Nov 2004 Posts: 43
|
I am getting a few of these errors on my AIX hub but it doesn't give an indication as to where it comes from.... Can anyone provide me any assistance...
11/24/04 19:08:22
AMQ7469: Transactions rolled back to release log space.
EXPLANATION:
The log space for the queue manager is becoming full. One or more long-running
transactions have been rolled back to release log space so that the queue
manager can continue to process requests.
ACTION:
Try to ensure that the duration of your transactions is not excessive. Consider
increasing the size of the log to allow transactions to last longer before the
log starts to become full.
My INI file looks like this
Log:
LogPrimaryFiles=16
LogSecondaryFiles=4
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=512
LogPath=/MQHA/A1PAPA01/log/A1PAPA01/
LogWriteIntegrity=SingleWrite
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/mqm/lib/amqzfu
ComponentDataSize=0
Channels:
MaxChannels=1000
MaxActiveChannels=1000
MQIBindType=FASTPATH
TCP:
KeepAlive=YES
ListenerBacklog=1000
SndBuffSize=131072
RcvBuffSize=131072
Thanks
-- jeramy |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Nov 30, 2004 1:09 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Check your channels. I bet you've got a too-big-for-your-logs batch on an incoming xmit queue on some other QM. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
csmith28 |
Posted: Tue Nov 30, 2004 1:26 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Whether or not what Jeff says is the case you may need to or you can increase the number of logs (assuming yo have enough space) by editing the /var/mqm/qmgrs/QMGR/qm.ini file for the MQManager then bouncing the MQManager.
LogPrimaryFiles=32 or 24 or something like that.
Then have a good look at what the WMQ Systems Administration Guide has to say about logging. Just to make sure there is no confusion.
We are talking about the log files located in /var/mqm/log/MQMGR/active not the AMQERR0*.LOG's.
You don't want your active logs to be wrapping to fast. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
xxx |
Posted: Wed Dec 01, 2004 11:57 am Post subject: |
|
|
Centurion
Joined: 13 Oct 2003 Posts: 137
|
There may be an Application issue also, I had once an application which went to loop and was not able to commit the the messages , |
|
Back to top |
|
 |
noles321 |
Posted: Wed Dec 01, 2004 12:09 pm Post subject: More info |
|
|
Apprentice
Joined: 15 Nov 2004 Posts: 43
|
Here is some more info... This is mainly a pass through hub and has no applications running on the box... It is mainly used as a front end with the exception of one client that connects, all other messages go straight through to another xmitq and out of the box.
thanks |
|
Back to top |
|
 |
csmith28 |
Posted: Wed Dec 01, 2004 1:14 pm Post subject: Re: More info |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
noles321 wrote: |
Here is some more info... This is mainly a pass through hub and has no applications running on the box... It is mainly used as a front end with the exception of one client that connects, all other messages go straight through to another xmitq and out of the box.
thanks |
Have a look at the files in /var/mqm/log/MQMGR/active...
Run and ls -ltr and tell us what the oldest and newest time stamps are.
You may need to increase your number of logs like I said before. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
|