Tapestry 5
  1. Tapestry 5
  2. TAP5-593

Calling ApplicationStateManager.exists() will throw an exception when the session has been invalidated

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.1
    • Fix Version/s: 5.1.0.2
    • Component/s: None
    • Labels:
      None

      Activity

      Hide
      Joachim Van der Auwera added a comment -

      It seems to hav been fixed in some cases only. I now get the exception later, but still on a ApplicatstateManager.exists() call.

      java.lang.IllegalStateException: getAttribute: Session already invalidated
      	org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:1032)
      	org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:110)
      	org.apache.tapestry5.internal.services.SessionImpl.getAttribute(SessionImpl.java:53)
      	org.apache.tapestry5.internal.services.SessionApplicationStatePersistenceStrategy.exists(SessionApplicationStatePersistenceStrategy.java:77)
      	$ApplicationStatePersistenceStrategy_12048ba2d10.exists($ApplicationStatePersistenceStrategy_12048ba2d10.java)
      	org.apache.tapestry5.internal.services.ApplicationStateManagerImpl$ApplicationStateAdapter.exists(ApplicationStateManagerImpl.java:55)
      	org.apache.tapestry5.internal.services.ApplicationStateManagerImpl.exists(ApplicationStateManagerImpl.java:143)
      	$ApplicationStateManager_12048ba2c7d.exists($ApplicationStateManager_12048ba2c7d.java)
      	org.equanda.t5nav.internal.NavigationPersistentFieldStrategy.getContextFromASO(NavigationPersistentFieldStrategy.java:98)
      
      
      Show
      Joachim Van der Auwera added a comment - It seems to hav been fixed in some cases only. I now get the exception later, but still on a ApplicatstateManager.exists() call. java.lang.IllegalStateException: getAttribute: Session already invalidated org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:1032) org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:110) org.apache.tapestry5.internal.services.SessionImpl.getAttribute(SessionImpl.java:53) org.apache.tapestry5.internal.services.SessionApplicationStatePersistenceStrategy.exists(SessionApplicationStatePersistenceStrategy.java:77) $ApplicationStatePersistenceStrategy_12048ba2d10.exists($ApplicationStatePersistenceStrategy_12048ba2d10.java) org.apache.tapestry5.internal.services.ApplicationStateManagerImpl$ApplicationStateAdapter.exists(ApplicationStateManagerImpl.java:55) org.apache.tapestry5.internal.services.ApplicationStateManagerImpl.exists(ApplicationStateManagerImpl.java:143) $ApplicationStateManager_12048ba2c7d.exists($ApplicationStateManager_12048ba2c7d.java) org.equanda.t5nav.internal.NavigationPersistentFieldStrategy.getContextFromASO(NavigationPersistentFieldStrategy.java:98)
      Hide
      Howard M. Lewis Ship added a comment -

      Are you sure about the code version you are running. Is there any possibility you invalidated the session but not via Session.invalidate() ... i.e., if you invalidate the HttpSession directly, you can still get this.

      Show
      Howard M. Lewis Ship added a comment - Are you sure about the code version you are running. Is there any possibility you invalidated the session but not via Session.invalidate() ... i.e., if you invalidate the HttpSession directly, you can still get this.
      Hide
      Joachim Van der Auwera added a comment -

      re-testing using 5.1.0.3 this is indeed fixed

      Show
      Joachim Van der Auwera added a comment - re-testing using 5.1.0.3 this is indeed fixed

        People

        • Assignee:
          Howard M. Lewis Ship
          Reporter:
          Joachim Van der Auwera
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development