The TDM portal version is 4.9.324.0
The two TDM Portal log files are throwing a lot of below errors:
startup log errors:
FINEST|1620/0|21-09-22 13:38:24|
FINEST|1620/0|21-09-22 13:40:16|Sep 22, 2021 1:40:16 PM com.ca.tdm.eventserviceclient.EventServiceClient postEventsFromQueue
FINEST|1620/0|21-09-22 13:40:16|WARNING: Error of type 500 occurred while sending queue event
FINEST|1620/0|21-09-22 13:40:16|com.ca.tdm.eventserviceclient.exception.EventPostException: Failed to post event, returned response code was 500 and reason
FINEST|1620/0|21-09-22 13:40:16| at com.ca.tdm.eventserviceclient.EventServiceClient.postEventEx(EventServiceClient.java:104)
FINEST|1620/0|21-09-22 13:40:16| at com.ca.tdm.eventserviceclient.EventServiceClient.postEventsFromQueue(EventServiceClient.java:141)
FINEST|1620/0|21-09-22 13:40:16| at com.ca.tdm.eventserviceclient.EventServiceClient$1.run(EventServiceClient.java:167)
FINEST|1620/0|21-09-22 13:40:16| at java.util.TimerThread.mainLoop(Timer.java:555)
FINEST|1620/0|21-09-22 13:40:16| at java.util.TimerThread.run(Timer.java:505)
TDMService Log:
2021-09-22 12:43:34.936 UTC [ERROR] [https-openssl-nio-8443-exec-3] --- [U:][M:][P:] c.c.t.s.JWTVerificationFilter: Missing or invalid authorization header. null
TDM Portal 4.9.1+
Both these errors are known to development teams.
The WARNING "WARNING: Error of type 500 occurred while sending queue event" is logged when telemetry is not configured and can be ignored.
The ERROR, " Missing or invalid authorization header. null", can also be safely ignored and since the message doesn't indicate/cause any trouble, this is on a low priority backlog to be handled/removed from logging.