SEVERE message in Server logs
Hi Team,
We are getting following SEVERE message repeatedly in server logs.
2013-07-11 17:26:35 SEVERE [DefaultSystemIDCache] Unable to obtain the systemprofile id string for internal systemprofile id: 3
2013-07-11 17:26:35 SEVERE [DefaultSystemIDCache] Unable to obtain the systemprofile id string for internal systemprofile id: 3
2013-07-11 17:26:35 SEVERE [DefaultSystemIDCache] Unable to obtain the systemprofile id string for internal systemprofile id: 3
Please suggest,why these are occurring?
Regards,
Jalpesh
Anybody????
Please open a support ticket for this
I have the same error in one of the current POv. I have logged a case with support as well. Have not gotten any response yet.
This log spamming should not have any effect on the application - what is the real problem (other than the log spamming)?
You can ask support for a fixpack to remove the log spam, refer to JLT-77080.
Best, Roman
Greertinds,
Similar issue at my side. Dynatrace application is getting restared and before the restart I could see the following logs.
2014-09-25 16:47:27 WARNING [DefaultSystemIDCache] Unable to obtain the systemprofile id string for internal systemprofile id: 3
2014-09-25 16:47:27 WARNING [DefaultSystemIDCache] Unable to obtain the systemprofile id string for internal systemprofile id: 4
2014-09-25 16:51:18 INFO [ShutdownPipe] got shutdown command on named pipe
2014-09-25 16:51:19 INFO [Server] Shutting down server...
2014-09-25 16:51:19 INFO [Server] Shutting down repository...
2014-09-25 16:51:19 INFO [TunnelHttpServer] tunnel http server listening on :8023 stopped.
2014-09-25 16:51:19 INFO [TransactionSplitter] syncing system profile 'dynaTrace Self-Monitoring'.
2014-09-25 16:51:19 INFO [Server] Repository is now stopped
2014-09-25 16:51:19 INFO [Scheduler] [dynaTrace Server] Shutting down
Does anyone have the solution already?
Thanks in Advance,
Hi. As Roman said in his previous response - there is a FixPack available for 5.5. Which version are you using?
If you run on 5.5 please request a fixpack for that log spamming problem. It is really just about log spamming but not a real problem with dynaTrace
Hi Andreas Grabner,
Thakn you for the reaction.
Maybe this is the log spamming, however in my case dynatrace application got restarted automatically and before the restart I could only find these logs. Also this is not the first time, we could see the same logs each time this issue happens
I have raised a ticket already. Let's see what compuware says.
