SAP B1 HANA - Catalina.out full of WARN/ERROR msgs

Hello all, we conscionable discovered that the "catalina.out" log record handled by tomcat connected the SAP HANA Server for SAP Business One person been increasing dilatory implicit a fewer months. Last week we discovered the log record was astir 900GB. 

After cleaning this record and waiting for it to capable again with immoderate data, we discovered that astir each 2nd these errors are written successful the file:

2024-12-02 07:47:47 ERROR [https-jsse-nio-40000-exec-52] com.sap.b1.sdk.oidc.core.handler.OAuth2Handler - not a valid token io.jsonwebtoken.ExpiredJwtException: JWT expired astatine 2024-11-20T14:05:15Z. Current time: 2024-12-02T06:47:47Z, a quality of 1010552043 milliseconds. Allowed timepiece skew: 0 milliseconds. at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:427) at io.jsonwebtoken.impl.ImmutableJwtParser.parse(ImmutableJwtParser.java:148) at com.sap.b1.sdk.oidc.core.handler.OAuth2Handler.validateAccessToken(OAuth2Handler.java:174) at com.sap.b1.sdk.oidc.core.handler.OAuth2Handler.validateAccessToken(OAuth2Handler.java:218) at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.parseAndValidate(OAuth2TokenFilter.java:183) at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.handleAuthorizationHeader(OAuth2TokenFilter.java:125) at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.doFilter(OAuth2TokenFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:838) 2024-12-02 07:48:01 WARN [https-jsse-nio-40000-exec-71] com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter - cheque authorization header error com.sap.b1.sdk.oidc.core.exception.B1SDKNotAuthenticatedException: invalid entree token at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.parseAndValidate(OAuth2TokenFilter.java:185) at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.handleAuthorizationHeader(OAuth2TokenFilter.java:125) at com.sap.b1.sdk.oidc.web.filter.OAuth2TokenFilter.doFilter(OAuth2TokenFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:181) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:156) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:598) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:617) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:838)

I was not capable to find immoderate documentation oregon SAP enactment astir this subject. Given the information that it is writting these ERROR/WARN each seconds, I would similar to cognize if this is mean oregon not and if it's not normal, however to close this issue? 

File determination is here: /hana/usr/sap/SAPBusinessOne/Common/tomcat/logs

Since we discovered this, astatine the infinitesimal we "clean" this record utilizing the pursuing cmd each time with cron: 

cat /dev/null > /hana/usr/sap/SAPBusinessOne/Common/tomcat/logs/catalina.out

Thank you.

Best regards