2024 Dec 03 7:45 AM - edited 2024 Dec 03 7:47 AM
Hello all, we just discovered that the "catalina.out" log file handled by tomcat on the SAP HANA Server for SAP Business One have been growing slowly over a few months. Last week we discovered the log file was about 900GB.
After cleaning this file and waiting for it to fill again with some data, we discovered that almost every second these errors are written in 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 at 2024-11-20T14:05:15Z. Current time: 2024-12-02T06:47:47Z, a difference of 1010552043 milliseconds. Allowed clock 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 - check authorization header error
com.sap.b1.sdk.oidc.core.exception.B1SDKNotAuthenticatedException: invalid access 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 able to find any documentation or SAP note about this subject. Given the fact that it is writting these ERROR/WARN every seconds, I would like to know if this is normal or not and if it's not normal, how to correct this issue?
File location is here: /hana/usr/sap/SAPBusinessOne/Common/tomcat/logs
Since we discovered this, at the moment we "clean" this file using the following cmd every day with cron:
cat /dev/null > /hana/usr/sap/SAPBusinessOne/Common/tomcat/logs/catalina.out
Thank you.
Best regards
Request clarification before answering.
Hi Private_Member_715690
Regarding the large size of catalina.out log file, please refer to SAP Note SAP Note 3387058 - The size of tomcat logs is rapidly increasing.
Thank You.
Kind Regards
Nidhi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
60 | |
8 | |
8 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.