Getting this error suddenly in one of tomcat instance about btm HOT 5 CLOSED

I can only think of two reasons that can cause logs to corrupt themselves:

1. Have two instances of BTM use the exact same log files. Normally this is prevented by the use of file locks, but there are way around that, like storing the files on NFS. Don't do that: each JVM must have its unique pair of log files, and they should be on a locally-attached disk.

2. Hardware failure. It's way more common that most people think, and unless you tell me that your files are sitting on ZFS and the latter isn't reporting any error this can never be ruled out.

from btm.

I just deleted the btm1.btm and btm2.btm files under work folder of tomcat instance and then my problem seems to be resolved, I am not sure if this is the right way to do?

from btm.

You've just thrown your atomicity out the window by doing that. Those files are as critical as your data itself, you should store them on a reliable and backed up disk.

The BTM jar does contain a swing UI you can use to analyse the contents of the log files, maybe you could start with that?

from btm.

I dint knew that the BTM jar has swing UI to analyse the contents of the log files, Thats great, How can I access that?

from btm.

Your best starting point is to read the code of this class: https://github.com/bitronix/btm/blob/master/btm/src/main/java/bitronix/tm/gui/Console.java

This is a quick an dirty tool I wrote to help me analyze the raw contents of the log files, and it's very bare bones: don't expect a nice polished tool that will do some magic to give you some precise answer but rather a clunky one that will point you to where in the files is the corruption. It's then up to you to understand the format and other implementation details (there are quite some comments in the source describing that) to try to figure out what happened.

It's tedious but rewarding once you know your way.

from btm.