SEVERE: Session event listener threw exception after Web Client upgrade to 14.0.5
search cancel

SEVERE: Session event listener threw exception after Web Client upgrade to 14.0.5

book

Article ID: 139515

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

After the upgrade of CA Vantage Web Client from 14.0.4 to 14.0.5 , the following message was issued issued in the TOMCAT STC:

 

SEVERE: Session event listener threw exception

 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userSessionBean': Scope 'session' is not act

 ive for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exc

 eption is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actu

 al web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web reque

 st and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use R

 equestContextListener or RequestContextFilter to expose the current request.

  at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:341)

  at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:191)

  at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1127)

  at com.ca.vantage.cmn.util.SpringUtil.getBean(SpringUtil.java:25)

  at com.ca.vantage.ews.UserSessionBean.getInst(UserSessionBean.java:126)

  at com.ca.vantage.ews.ConnectionPool.logoffCurrentSession(ConnectionPool.java:93)

  at com.ca.vantage.cmn.sys.VantageSessionListener.sessionDestroyed(VantageSessionListener.java:41)

  at org.apache.catalina.session.StandardSession.expire(StandardSession.java:837)

  at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:695)

  at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:666)

  at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:651)

  at org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:5680)

  at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1377)

  at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)

  at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1381)

  at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1349)

  at java.lang.Thread.run(Thread.java:812)

 Caused by: java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an act

 ual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web requ

 est and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use

 RequestContextListener or RequestContextFilter to expose the current request.

  at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131)

  at org.springframework.web.context.request.SessionScope.get(SessionScope.java:90)

  at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:327)

  ... 16 more

 

Environment

Release : 14.0

Component : CA Vantage Storage Resource Manager

Resolution

Web Client 14.0.06, available with PTF SS10309, contains the fix for this problem.