Running a report with visualize.js error when session times out

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: An Authentication object was not found in the SecurityContext
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(
        at com.sun.proxy.$Proxy119.cancelExecution(Unknown Source)
        at org.springframework.web.context.request.DestructionCallbackBindingListener.valueUnbound(
        at org.apache.catalina.session.StandardSession.removeAttributeInternal(
        at org.apache.catalina.session.StandardSession.expire(
        at org.apache.catalina.session.StandardSession.isValid(
        at org.apache.catalina.session.ManagerBase.processExpires(
        at org.apache.catalina.session.ManagerBase.backgroundProcess(
        at org.apache.catalina.core.ContainerBase.backgroundProcess(
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
        at org.apache.catalina.core.ContainerBase$
tyson.decker's picture
Joined: Nov 13 2014 - 2:27pm
Last seen: 6 years 10 months ago

I've tried authenticating using hooks, and just providing the username / password in the auth variable. Both produced the same stack trace. 

tyson.decker - 7 years 10 months ago

I am using the Rest API and facing the same issue. When the session times out, it produces this stack trace.

balaji.paulrajan - 7 years 10 months ago

I am also gettng the same issue , Can it be ignored. Does it cause  any performance/memory issue.



madhusudangoudk - 6 years 4 months ago

1 Answer:

Probably because authentication object becomes invalid. When using APIs and Visualize.js, users have to take care of errors.

Recommend increasing session timeout.

It's  "session-timeout" setting in web.xml.

hozawa's picture
Joined: Apr 24 2010 - 4:31pm
Last seen: 3 years 9 months ago