Debug in tm1s-log.properties cause TM1s service down

[Brian_Q]

Hi,
In case anybody meet similar issue, I would like to share one case as below:

1. Stop service, turn debug on in tm1s-log.properties
#log4j.logger.TM1=INFO, S1
log4j.logger.TM1=DEBUG, S1
TM1 service couldn't be restarted.

In TM1server.log, it shows:
...
TM1.Event mt_WaitForSingleObject: Waiting for event 0x00000000000001C4.

Workaround from IBM:
Start TM1 services,
log4j.logger.TM1=INFO, S1
#log4j.logger.TM1=DEBUG, S1

, update tm1s-log.properties while service is running.

Then debug information is populated into TM1Server.log and TM1 server works fine.

Cheers

[qml]

The affected TM1 version(s) would be helpful too. As would the PMR/APAR numbers. With this info we can move the thread to the Bugs subforum. Thanks for sharing.

[lotsaram]

Hi,
In case anybody meet similar issue, I would like to share one case as below:

1. Stop service, turn debug on in tm1s-log.properties
#log4j.logger.TM1=INFO, S1
log4j.logger.TM1=DEBUG, S1
TM1 service couldn't be restarted.

In TM1server.log, it shows:
...
TM1.Event mt_WaitForSingleObject: Waiting for event 0x00000000000001C4.

Workaround from IBM:
Start TM1 services,
log4j.logger.TM1=INFO, S1
#log4j.logger.TM1=DEBUG, S1

, update tm1s-log.properties while service is running.

Then debug information is populated into TM1Server.log and TM1 server works fine.

Cheers

Well maybe it's not a bad thing that debug logging wasn't able to be switched on during server startup. If you plan to have debug level logging for all loggers and not just 1 or 2 point specific ones during the whole of the server startup then I hope you have at least 100 GB of disk free, coz you will need it.

[kangkc]

This is a known bug in 10.2.2. If I am not wrong it is resolved in FP4 but I can't be 100% sure.