IBM Support

Tm1 Server log ends logging - ERROR IN LOGGER LAYER: Bad log message size - bringing shared memory reader down

Troubleshooting


Problem

Tm1 Server ends logging and displays the following line:

 

ERROR IN LOGGER LAYER:
Bad log message size - bringing shared memory reader down

 

Symptom

Tm1 Server ends logging and displays the following line:

 

ERROR IN LOGGER LAYER:
Bad log message size - bringing shared memory reader down

Cause

The way logging works in TM1 is that a buffer of shared memory is allocated from the OS and then the server writes messages to this buffer, while the reader reads those messages and writes them to disk.

The server and reader have an agreed-upon maximum log message size - the server will never write a message to shared memory that exceeds this size.

If this log message size is at its maximum the TM1 Server will stop to write to the tm1server.log and will add the following line: ERROR IN LOGGER LAYER:
Bad log message size - bringing shared memory reader down
 

Environment

Win 64

Resolving The Problem

Each SaveDataAll is setting this back to zero.
The default setting of the maximum log size is 5 MB.
This can be raised to max 20 MB by adding this line to the tm1s-log.properties file:
log4j.appender.S1.MemorySize=20

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9RXT","label":"Cognos TM1"},"Component":"tm1 Server","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"all Versions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 October 2018

UID

ibm10735355