Skip to content

Fixes ISSUE-50770: Increases the log verbosity when a session is destroyed

If the TRACE log level is activated in SessionListener, whenever a session is terminated the stack trace will be printed like this:

2022-11-08 08:47:36,977 [http-nio-8080-exec-2] TRACE org.openbravo.erpCommon.security.SessionListener - Stack trace: org.openbravo.base.exception.OBException: null at org.openbravo.erpCommon.security.SessionListener.deactivateSession(SessionListener.java:198) [classes/:?] at org.openbravo.erpCommon.security.SessionListener.sessionDestroyed(SessionListener.java:70) [classes/:?] at org.apache.catalina.session.StandardSession.expire(StandardSession.java:824) [catalina.jar:8.5.24] at org.apache.catalina.session.StandardSession.expire(StandardSession.java:766) [catalina.jar:8.5.24] at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1266) [catalina.jar:8.5.24] at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:171) [catalina.jar:8.5.24] at org.openbravo.client.kernel.BaseKernelServlet.invalidateSession(BaseKernelServlet.java:96) [classes/:?] at org.openbravo.base.secureApp.HttpSecureAppServlet.logout(HttpSecureAppServlet.java:598) [classes/:?] at org.openbravo.client.kernel.BaseKernelServlet.service(BaseKernelServlet.java:63) [classes/:?] at org.openbravo.client.kernel.KernelServlet.service(KernelServlet.java:170) [classes/:?] at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) [servlet-api.jar:?]

That should help us understand why sometimes sessions are terminated without any apparent reason

Merge request reports