Discussion:
TDI ibmdi.log issues
(too old to reply)
d***@gmail.com
2019-03-08 16:18:42 UTC
Permalink
Hello,

We created a new TDI Assembly line and store it in the workspace directory where other Assembly lines are also running. However, when we restart the dispatcher, messages are being stored in "ibmdi.log.*" instead of the primary ibmdi.log file. It doesn't appear to be a sizing issue as we have the configuration to roll over after 10MB. The file sizes are not close to 10MB. So, for some reason, the messages are bypassing the "ibmdi.log" and immediately logging to "ibmdi.log.Number", i.e. "ibmdi.log.2". Has anyone ever seen this behavior?

Thanks,
Derrick Chapman
Franzw
2019-03-10 10:08:32 UTC
Permalink
Post by d***@gmail.com
Hello,
We created a new TDI Assembly line and store it in the workspace directory where other Assembly lines are also running. However, when we restart the dispatcher, messages are being stored in "ibmdi.log.*" instead of the primary ibmdi.log file. It doesn't appear to be a sizing issue as we have the configuration to roll over after 10MB. The file sizes are not close to 10MB. So, for some reason, the messages are bypassing the "ibmdi.log" and immediately logging to "ibmdi.log.Number", i.e. "ibmdi.log.2". Has anyone ever seen this behavior?
Thanks,
Derrick Chapman
I have not seen that as a default behavior. I would look into the soldir/etc log4j.properties to see if this has been altered.

You should also raise a PMR/case if the reason is not uncovered in the property file...

HTH
Regards
Franz Wolfhagen
j***@gmail.com
2019-03-11 04:29:17 UTC
Permalink
By default, every time you start a TDI server, the old ibmdi.log will be renamed to ibmdi.log.1, the previous ibmdi.log.1 will be named ibmdi.log.2, and so on.

So suppose you start a TDI server. It will begin logging to ibmdi.log.

Then you start a new TDI server, and the first TDI server will now log to ibmdi.log.1, while the new TDI server will log to ibmdi.log.

If you now start yet another TDI server, that TDI server will log to ibmdi.log, while the previous TDI server will log to ibmdi.log.1, and the first TDI server will log to ibmdi.log.2.

You now have 3 different TDI servers running, logging to different files.

If a rollover due to file size happens, the TDI server that have to do the rollover will begin logging to ibmdi.log, while all the other TDI servers will have the log file name bumped by one.

You can change the behavior by modifying etc/log4j.properties. The default appender is the TDIRollingFileAppender, which behaves like this:

## TDIRollingFileAppender behaves like org.apache.log4j.RollingFileAppender, except that it also
## rolls over log files when opening the log files, if Append=false.
## The RollingFileAppender rolls over log files when they reach a certain size
## specified by the MaxFileSize parameter, and the number of backup files is specified by MaxBackupIndex
Loading...