View process rollback and restart messages in TM1 logs
This update makes it easier to detect lock exceptions for TurboIntegrator processes, and makes it easier to process the tm1server.log file with automation tools. When a TurboIntegrator process rolls back and restarts, the process is now represented in the tm1server.log file as three steps: starting, restarting because of lock contention or rollback, and then finishing. An entry was added to the tm1server.log file that shows the TurboIntegrator process as restarting due to lock contention or rollback instead of just starting. This logging is enabled by default without setting any specific debug options.
Example log
2364 [15] INFO 2019-01-09 20:30:37.986 TM1.Process Process "Diag.LockTest.DimensionWrite1" executed by user "CJP/stuart"
17088 [15] INFO 2019-01-09 20:30:37.987 TM1.Process Process "Diag.LockTest.DimensionWrite2" executed by user "CJP/stuart"
17088 [15] INFO 2019-01-09 20:30:41.058 TM1.Process Process "Diag.LockTest.DimensionWrite2" rolled back due to lock exception (2364). Process will restart automatically"
2364 [15] INFO 2019-01-09 20:30:41.054 TM1.Process Process "Diag.LockTest.DimensionWrite1": finished executing normally, elapsed time 3.07 seconds
17088 [15] INFO 2019-01-09 20:30:41.058 TM1.Process Process "Diag.LockTest.DimensionWrite2" executed by user "CJP/stuart"
17088 [15] INFO 2019-01-09 20:30:44.064 TM1.Process Process "Diag.LockTest.DimensionWrite2": finished executing normally, elapsed time 3.00 seconds