|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Linear logging - log not created |
« View previous topic :: View next topic » |
Author |
Message
|
sac063 |
Posted: Mon Nov 22, 2004 6:31 am Post subject: Linear logging - log not created |
|
|
Apprentice
Joined: 23 Jan 2004 Posts: 36
|
Hi again guys...
Hit a very interesting problem but about the same old linear logging. I am running a queue manager with linear logging, log size of 40MB. primary 5 and secondary 3 logs in number.
This was according to calculation. But I tried to stress the system by pouring messages at a very high rate and the result is below -
The log for queue manager SGUKLMB is full.
" 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.
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 "
Something that is bothering me is...why was another log not created given there was enough directory space ? It is after all liner logging ?
Will be qreat if somebody can clear this puzzle
Cheers |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Nov 22, 2004 6:56 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
From the error message:
Quote: |
This situation may be encountered during a period of unusually high message traffic. |
This is just what you were doing!
The active log is updated at a checkpoint, which normally takes place after every 10000 queue operations, or when the queue is getting full. Naturally the checkpoint itself takes time, so if it does not complete (freeing log space) before the log is filled then you will get this message.
The solution is to define more and larger logs. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|