Log4j configuration in TDISOL / Custom ibmdi.log file rotation

HCL Connections Connections Forum
,
1

Hi Community,

is anybody else experiencing an issue with log rotation of ibmdi.log in the TDISOL package?

I had configured/enabled the DailyRollingFileAppender in etc/log4j.properties and ibmdi.logs had been rotated / back-up as for example ibmdi.log.2022-04-06. This was working fine in the past.

However, since some time I see that only ibmdi.log and 3 historical files (ibmdi-1.log, ibmdi-2.log and ibmdi-3.log) are kept. The DailyRollingFileAppender configuration seems not to be considered. I assume that this happened as part of the update to the latest TDISOL package named "HCL Connections v7.0 TDISOL Java 8 Support for Linux (2202)", but not sure.

Actually, today I wanted to enable tracing via etc/log4.properties but no additional logs are written. That's why I am wondering if log4j is still used by TDISOL package, especially since replacing log4j v1.x libraries.

Any other experiences?

Greetings

Maik

2

Hi Mark,

This Fix Pack contains fixes for SDI 7.2. Upgrades to log4j version 2.17.1.

Log4j upgrade.

SDI 7.2 Fix Pack 8 upgrades the log4j version to 2.17.1. Following are some additional details related to log4j changes.

  • The etc/log4j.properties will no longer be used. The server uses etc/log4j2.xml.
  • The old etc/log4j.properties will remain available for viewing, as unique logging may have been added.
  • The naming convention for old log files is slightly different, with the version number in front of ".log".
  • Feel free to make local changes in etc/log4j2.xml to try out exciting new log4j v2 features.
  • .....

7.2.0-ISS-SDI-FP0008 (ibm.com)

3

Hi Jason,

that's interesting to know, many thanks. I should read the README for fixpack updates from time to time ;-) But interesting, that the TDISOL package provided by HCL has not been updated accordingly or provided information about the changes around log4j 2.x.

Will try it out ...

Greetings

Maik

4

Example of my current TDISOL/etc/log4j2.xm file:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="info">
<Appenders>
<!-- The default SDI log file -->
<RollingFile name="Default"
append="true"
fileName="logs/ibmdi.log"
filePattern="logs/ibmdi-%i.log">
<PatternLayout pattern="%d{DEFAULT} %-5p [%c] - %m%n" />
<Policies>
<OnStartupTriggeringPolicy minSize="1" />
<SizeBasedTriggeringPolicy size="10MB" />
</Policies>
<DefaultRolloverStrategy max="3" fileIndex="min" />
</RollingFile>

<!-- Some messages will be logged to the console (standard out) -->
<Console name="CONSOLE" target="SYSTEM_OUT">
<PatternLayout pattern="[%t] %-5p - %m%n"/>
</Console>

<RollingFile name="SCIM"
append="true"
fileName="SCIM/logs/audit.log"
filePattern="SCIM/logs/audit.%d{yyyy-MM-dd}.log">
<PatternLayout pattern="%m%n" />
<Policies>
<TimeBasedTriggeringPolicy />
</Policies>
<DefaultRollOverStrategy />
</RollingFile>
</Appenders>

<Loggers>
<Root level="debug">
<AppenderRef ref="Default"/>
</Root>
<Logger name="Console" level="warn" >
<AppenderRef ref="CONSOLE"/>
</Logger>

<Logger name="com.ibm.di.config" level="warn" >
<AppenderRef ref="CONSOLE"/>
</Logger>
<Logger name="com.ibm.di.TDIProperties" level="warn" >
<AppenderRef ref="CONSOLE"/>
</Logger>
<Logger name="com.ibm.di.loader" level="warn" >
</Logger>
<Logger name="org.apache.wink" level="error" >
</Logger>
<Logger name="com.ibm.di.ScimService" level="info" additivity="false">
<AppenderRef ref="SCIM"/>
</Logger>
</Loggers>
</Configuration>