Expired or unknown session token should not be handled as an error

Current Situation

After a login into JOC Cockpit the session timeout is active. When there is no click until the session expires, the login screen is shown

The login screen shows an unknown session exception if api calls have been executed after the expiration.

The log file contains

• Log entries with the categorie ERROR e.g.
  • ERROR qtp606548741-21 c.s.j.c.JOCDefaultResponse - SessionNotExistException
• a stacktrace for an ExpiredSessionException
• several stacktraces for some UnknownSessionException

Desired Behavior

An api call with an unknown or expired access token should not be considered as an error. It should be reported in the log file with the category INFO like this

2021-11-10T15:48:19,219 INFO qtp606548741-13 c.s.j.c.JOCDefaultResponse - UnknownSessionException: There is no session with id [ffb7646e-9d63-4c04-ba5a-a8fa141e5f11]
{{ INFO qtp606548741-20 c.s.j.c.JOCDefaultResponse - Authentication failure}}

There should be no stacktrace in the log file. The http response code is 401 Unauthorized