MQSeries.net :: View topic - Primary and Secondary Log sizes

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Primary and Secondary Log sizes

Primary and Secondary Log sizes

« View previous topic :: View next topic »

Author

Message

kdavis

Posted: Wed Mar 19, 2003 6:53 am Post subject: Primary and Secondary Log sizes

Novice

Joined: 09 Dec 2002
Posts: 13

Is there a rule of thumb or experience driven rule for setting these sizes?

Thanks,

Keith

tillywern

Posted: Wed Mar 19, 2003 12:07 pm Post subject: Log file sizes.

Centurion

Joined: 28 Jan 2003
Posts: 109
Location: Colorado

Log file number and size are generally derived from message volume. Experience will generally be the best guide. Error on the size of caution as disk is generally cheap.

It is important to know what type of information is being stored in queues. High volume persistent traffic will require more logs and you will probably want to use linear logging. This is also true of queue managers where messages are stored for batch processing.

Online pseudo real-time applications may not require much logging at all because that data is only held in MQ for transit.

MQSeries generates events that tell you when a log file can be archived or removed from the system. From the programming side applications should properly use sync points to keep MQ from keeping logs around due to uncommitted reads or writes.

Hope this gets you started.

kdavis

Posted: Thu Mar 20, 2003 6:08 am Post subject: Re: Log file sizes.

Novice

Joined: 09 Dec 2002
Posts: 13

tillywern wrote:

...Hope this gets you started.

Thanks. We ar using MQ as the JMS provider, so it's hard to predict what the soze / volume will be. I'll look into using the generated events to trigger log deletion...

tillywern

Posted: Thu Mar 20, 2003 1:32 pm Post subject:

Centurion

Joined: 28 Jan 2003
Posts: 109
Location: Colorado

If you are using JMS you can run into some difficulties with some common MQ architectures/functions such as a hub and spoke architecture or message forwarding since JMS wants to respond directly back to the queue manger where the initial request was made. At least that is what I saw when using JMS about 12 months ago.

It would probably be wise to either place volume capture logic on your message producers or consumers so you can track growth in message size or voloume.

Cheers

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Primary and Secondary Log sizes

Jump to:

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

Protected by Anti-Spam ACP