|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQIPT V2.0 maintenance |
« View previous topic :: View next topic » |
Author |
Message
|
ALCSALCS |
Posted: Wed Oct 28, 2009 1:05 am Post subject: MQIPT V2.0 maintenance |
|
|
Acolyte
Joined: 14 Apr 2002 Posts: 61
|
I have installed for the first time in our environment MQIPT V2.0 in Unix
Nobody in our environment has any experience with the product.
Some questions start to appear related with the maintenance of the product like
a) how much space should be allocated to the log/error and or trace files ?
b) are these files wraparound ?
c) For the log file I found a parameter MaxLogFileSize that you can define.
Reading the info in the manual it looks like they are a mechanism that erases automatically previous backups.
d) for error and trace files I have not find any documentation about sizing, etc
Is there some documentation/information available that can help me to deal with these issues ?
If someone has any information please let me know.
Many Thanks |
|
Back to top |
|
 |
PhilBlake |
Posted: Mon Nov 02, 2009 10:07 am Post subject: |
|
|
 Acolyte
Joined: 25 Oct 2005 Posts: 64
|
Quote: |
a) how much space should be allocated to the log/error and or trace files ? |
Each entry in the connection log can vary in size, depending on any errors, and there are usually 4 entries per successful connection, so if each entry averaged 200 bytes, then 10,000 successful connection requests would take about 8Meg disk space.
Trace files are written to the errors sub-directory only if tracing has been enabled (Trace=5). FDC files can be written to same directory, but if you're seeing these files, then you have a problem !
Quote: |
b) are these files wraparound ? |
Trace files do not wrap and log files are controlled by MaxLogFileSize.
Quote: |
c) For the log file I found a parameter MaxLogFileSize that you can define.
Reading the info in the manual it looks like they are a mechanism that erases automatically previous backups. |
Yes, if mqipt002.log exists and MaxLogFileSize has been reached again, then the old file is replaced. I'm not aware of anyone hitting this problem.
Quote: |
d) for error and trace files I have not find any documentation about sizing, etc |
This depends on a lot of factors, like how many routes are being used and how many connections are using each route, how many messages are being sent, etc. This could run into 100's megabytes.... if you try Trace=5, then you can see the sort of data being traced.
HTH,
Phil |
|
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
|
|
|
|