Author |
Message
|
mitch |
Posted: Tue Oct 07, 2003 4:54 am Post subject: Increasing the number of Primary/Secondary log files |
|
|
Apprentice
Joined: 19 Mar 2003 Posts: 25
|
Hi,
I have a queue manager running on a Windows 2000 server using the default number of primary/secondary logs. I increased the number of logs then bounced the q manager. However, it would appear that the new log settings have not taken affect.
I would have thought that bouncing the specific q manager would have been enough.
Anyone have any ideas
Cheers
Paul |
|
Back to top |
|
 |
dgolding |
Posted: Tue Oct 07, 2003 6:07 am Post subject: |
|
|
 Yatiri
Joined: 16 May 2001 Posts: 668 Location: Switzerland
|
I've just spent the last day or so on exactly the same problem. What you're seeing is absolutely correct.
The queue manager will only use what log files it needs. If a long running transaction of uncommited messages is running, then it will use more and more log files until it reaches its' limit (you'll get a 2003 transaction rolled back to release log space) or until they have all been successfully commited. But, if you don't have a transaction that uses more than 20Mb of log space, it won't use more than that. The default for windows/unix/etc is 5 x 4Mb (3 primary, 2Secondary).
You can either create the queue manager again, using the LP and LS ((primary and secondary) flags on the command line, OR, create a dummy queue(with a high max-depth) and use AMQSBLST (sample program) to put in thousands of uncommited messages. This will "stretch" your S0000[N].LOG files.
One suggestion:
amqsblst -c 10000 -b 10000 -u 10000 QNAME QMGRNAME
This will use up 10,000msgs of 10,000 bytes (plus header) space on your transaction logs - say roughly 100Mb or 25 4Mb log files. Have a play about.
Don't forget to clear the dummy queue when you're done!
HTH |
|
Back to top |
|
 |
morpheus |
Posted: Wed Oct 08, 2003 2:55 pm Post subject: changing log files setting. |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
Changing queue manager log properties won't actually increase the no. of log files ( I too had this problem).
To increase the no. of log files you have to recreate the queue manager with more no. of log parameters. If you want to avoid recreating queue manager, then you need to
* stop the queue manager
* create a dummy queue manger with desired log parameters
* copy the log files and amqhlctl.lfh file from dummy queue manager to real queue manager.
* Change the queue manager properties in qm.ini file and then
* restart the queue manager.
you'll see the new parameters take effect. Delete the dummy queue manager.
That should solve your problem.
Later
-morpheus |
|
Back to top |
|
 |
EddieA |
Posted: Wed Oct 08, 2003 3:27 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
No. You do NOT have to recreate a Queue Manager to increase the number of log files. As was pointed out earlier. Change the settings and stop/restart the Queue Manager. When it needs the extra files, it will create them.
The ONLY parameters that cannot be changed are the Log File Size and the Log File Type.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
morpheus |
Posted: Fri Oct 10, 2003 12:43 pm Post subject: log files |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
Eddie,
I got this wrong because when I restarted the queue manager with new parameters I couldn't find any increase in primary log files in active
directory. So are you saying although we don't see any increase queue manager will create the primary log files when they are needed?
I'll really appreciate if you can give me more insight into this
Thank you
-Sai |
|
Back to top |
|
 |
EddieA |
Posted: Fri Oct 10, 2003 10:30 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Yep, you got it right. MQ continues to use the curent settings untill it needs to increase them. The fact that you increased the primary log doesn't mean it automatically creates them.
Once you do expand the number of logs, it won't shrink then back below your 'new' primary setting.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
morpheus |
Posted: Mon Oct 13, 2003 7:30 am Post subject: |
|
|
 Acolyte
Joined: 08 Mar 2003 Posts: 72 Location: Austin, TX
|
Eddie,
Thank you very much. |
|
Back to top |
|
 |
|