| Author |
Message
|
| r00kie |
 Posted: Tue Jan 06, 2004 11:54 pm Post subject: Queue Manager Log file full? |
 |
|
Novice
Joined: 27 Aug 2002
Posts: 18
|
Hi,
Has anyone run across this and if so can anyone advise on a resolution?
We are running MQ5.3 on W2k server with 5 web servers as clients and have been receiving this message intermittently. This has actually caused the queue manager to shut down and will not restart without manual intervention. We have also had problems with the client channels ending abnormally and cannot find the root cause of the problem. I believe that the clients are running on W2K also with MQ 5.3 client.
Should we increase the log file size and if so, how do we do that?
Any advise is appreciated.
R00kie
AMQ7463: The log for queue manager XXXXXXX is full.
EXPLANATION:
This message is issued when an attempt to write a log record is rejected
because the log is full. The queue manager will attempt to resolve the problem.
ACTION:
This situation may be encountered during a period of unusually high message
traffic. However, if you persistently fill the log, you may have to consider
enlarging the size of the log. You can either increase the number of log files
by changing the values in the queue manager configuration file. You will then
have to stop and restart the queue manager. Alternatively, if you need to make
the log files themselves bigger, you will have to delete and recreate the queue
manager. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Wed Jan 07, 2004 1:03 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Did you try the System Administration Guide?
On Windows the number of log files can be found on the log tab of the queuemanager properties in MQSeries services.
Michael |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 07, 2004 10:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
We had the same problem and found an old MQ app that never commited its messages after the MQGET. It would take a copy of the message, update the DB, and consider the job done. After several hours, the logs would fill, the app would get a 2003 BACKED Error, which it didn't do anything with, and the cycle would start again. Since it was doing a get by corrrelID, it ignored these backed out messages until they expired. This went on for weeks, maybe even months.
The app never knew anything was wrong, we found the problem because of these messages in our error logs.
Look at the apps. They are probably written incorrectly. If they are going to get messages under syncpoint, they have to commit. And every interface with MQ should check the reason codes after every call to MQ, and actually do something with any error!
And in keeping with that theme, they probably dont disconnect properly from the QM when they do want to end, hence the client channels that seem to end abnormally (the channels have no choice, the app ended without cleaning up after itself).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bamboozled_by_MQ |
| Posted: Wed Jan 07, 2004 11:23 am Post subject: |
|
|
Voyager
Joined: 07 Jan 2004
Posts: 75
|
you should specify the transaction log size (to make them larger than the default sizes) when creating the QMgr.
i.e. CRTMQM....
-c = QMGR Description
-d = Default Transmission Queue
-h = Maximum # of Handles
-lc = Circular Logging
-ll = Linear Logging
-ld = Log Path
-lf = Log File Size <-----------------------------------------
-lp = Log Primary Files
-ls = Log Secondary Files
-q = Sets QMGR as Default
-g = Application Group
-t = Interval Value
-u = Dead Letter Queue
-x = Maximum Uncommitted Messages
-z = Suppress Error Messages
Last edited by bamboozled_by_MQ on Wed Jan 07, 2004 12:02 pm; edited 1 time in total |
|
| Back to top |
|
|
| Prahasith |
| Posted: Wed Jan 07, 2004 11:33 am Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
I agree with peter
1) Start doing some disconnects at regular intervals
2) Start committing messages at regular intervals |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 07, 2004 11:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bamboozled_by_MQ wrote: |
| you will need to specify the transaction log size when creating the QMgr. |
Actually, you don't need to specify a transaction log when you create the QM. You can allow it to take the defaults.
And you can change the NUMBER of primary log files and secondary log files at any point later.
But you can't change the SIZE without dropping and recreating the QM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| r00kie |
| Posted: Thu Jan 08, 2004 12:44 am Post subject: |
|
|
Novice
Joined: 27 Aug 2002
Posts: 18
|
Thanks so much for all your help on this. I didn't even know where to start looking but I did suspect it was app related. At least now I am pointed in the right direction.
I'll let you know how things turn out.
Sincere thanks,
R00kie |
|
| Back to top |
|
|
|
|
