2 Replies Latest reply on Feb 2, 2006 12:58 PM by Gavin King

    SeamListener: No Conversation Active

    ryan dewell Novice

      Still using beta 1.

      As recommended in the Seam docs, all of my beans have a method with @Destroy @Remove on them. Beyond that, these methods are no-ops.

      Yet, whenever the SeamListener runs to expire out the session, this shows up in the error logs:

      java.lang.IllegalStateException: No conversation context active
       at org.jboss.seam.ScopeType.getContext(Unknown Source)
       at org.jboss.seam.interceptors.RemoveInterceptor.removeIfNecessary(Unknown Source)
      etc....
      at $Proxy240.onDestroy(Unknown Source)
      


      Since my onDestroy method doesn't actually have any code in it, I have to believe this is coming from injection or something? How can I avoid this error? It appears to cause Seam to stop a proper removal process.

      Ryan

        • 1. Re: SeamListener: No Conversation Active
          ryan dewell Novice

          More of the stacktrace after my previous post:

           at org.jboss.seam.contexts.Contexts.callDestroyMethod(Unknown Source)
           at org.jboss.seam.contexts.Contexts.destroy(Unknown Source)
           at org.jboss.seam.contexts.Lifecycle.endSession(Unknown Source)
           at org.jboss.seam.servlet.SeamListener.sessionDestroyed(Unknown Source)
           at org.apache.catalina.session.StandardSession.expire(StandardSession.java:675)
           at org.apache.catalina.session.StandardSession.isValid(StandardSession.java:567)
           at org.apache.catalina.session.ManagerBase.processExpires(ManagerBase.java:655)
           at org.apache.catalina.session.ManagerBase.backgroundProcess(ManagerBase.java:640)
           at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1283)
          


          • 2. Re: SeamListener: No Conversation Active
            Gavin King Master

            There are bugfixes in this area in beta2.