| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Circular Log Wrap |
« View previous topic :: View next topic » |
| Author |
Message
|
| bobbee |
 Posted: Sat Jan 15, 2022 6:26 am Post subject: Circular Log Wrap |
 |
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
| Except for monitoring the log files, is there a way to tell (AMQ messages, Log Event, etc) that the Circular logging system has wrapped back to reuse the first log IE S000001.log |
|
| Back to top |
|
 |
| Andyh |
| Posted: Sat Jan 15, 2022 9:14 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Jan 16, 2022 8:24 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Andyh wrote: |
| Why would you care ? |
It could indicate that logs are undersized for the persistent message volume, or possible long running UOW. We look at log file time stamps when there are errors for transaction rollbacks.
_________________
Glenn |
|
| Back to top |
|
|
| Andyh |
| Posted: Mon Jan 17, 2022 8:59 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
You'd be getting AMQ7468 messages if transactions were being rolled back to release log space.
Best practice for circular logging is to size the primary log to be big enough for the expected workload. You can then use the presence of secondary extents as a signal to investigate why the log usage is higher than expected.
On recent releases, amqsrua gives you access to information relating to the log space usage that can help you size the log sensibly.
If I remember correctly, there was also a recent Hursley blog article by Mark Whitlock with good information on sizing the log. |
|
| 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
|
|
|
|
