After running a report using visualize.js and waiting for the users session to time out then the following stack trace is thrown. The stack trace is not thrown if running the report through the web interface. I'm using Jasper Reports Server 6.0.1. Not sure why this is happening. Does anybody have any help? Thanks
2015-05-12 15:40:52,217 ERROR RunReportServiceImpl,ContainerBackgroundProcessor[StandardEngine[Catalina]]:555 - Report execution cleanup failed:
org.springframework.security.authentication.AuthenticationCredentialsNotFoundException: An Authentication object was not found in the SecurityContext
at org.springframework.security.access.intercept.AbstractSecurityInterceptor.credentialsNotFound(AbstractSecurityInterceptor.java:339)
at org.springframework.security.access.intercept.AbstractSecurityInterceptor.beforeInvocation(AbstractSecurityInterceptor.java:198)
at org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:60)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy119.cancelExecution(Unknown Source)
at com.jaspersoft.jasperserver.remote.services.impl.RunReportServiceImpl.cancelReportExecution(RunReportServiceImpl.java:536)
at com.jaspersoft.jasperserver.remote.services.impl.RunReportServiceImpl.destroy(RunReportServiceImpl.java:549)
at org.springframework.beans.factory.support.DisposableBeanAdapter.destroy(DisposableBeanAdapter.java:239)
at org.springframework.beans.factory.support.DisposableBeanAdapter.run(DisposableBeanAdapter.java:215)
at org.springframework.web.context.request.DestructionCallbackBindingListener.valueUnbound(DestructionCallbackBindingListener.java:52)
at org.apache.catalina.session.StandardSession.removeAttributeInternal(StandardSession.java:1816)
at org.apache.catalina.session.StandardSession.expire(StandardSession.java:880)
at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:670)
at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:533)
at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:518)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1317)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1496)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1506)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1506)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1485)
at java.lang.Thread.run(Thread.java:745)
I've tried authenticating using hooks, and just providing the username / password in the auth variable. Both produced the same stack trace.
I am using the Rest API and facing the same issue. When the session times out, it produces this stack trace.
I am also gettng the same issue , Can it be ignored. Does it cause any performance/memory issue.
Thanks!