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

      Joachim Van der Auwera created issue -
      Howard M. Lewis Ship made changes -
      Field Original Value New Value
      Assignee Howard M. Lewis Ship [ hlship ]
      Howard M. Lewis Ship made changes -
      Status Open [ 1 ] In Progress [ 3 ]
      Howard M. Lewis Ship made changes -
      Summary exists on ApplicationStateManager causes an exception when the session has been invalidated Calling ApplicationStateManager.exists() will throw an exception when the session has been invalidated
      Howard M. Lewis Ship made changes -
      Status In Progress [ 3 ] Closed [ 6 ]
      Fix Version/s 5.1.0.2 [ 12313706 ]
      Resolution Fixed [ 1 ]
      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)
      Joachim Van der Auwera made changes -
      Resolution Fixed [ 1 ]
      Status Closed [ 6 ] Reopened [ 4 ]
      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
      Joachim Van der Auwera made changes -
      Status Reopened [ 4 ] Closed [ 6 ]
      Resolution Fixed [ 1 ]
      Transition Time In Source Status Execution Times Last Executer Last Execution Date
      Open Open In Progress In Progress
      3h 47m 1 Howard M. Lewis Ship 24/Mar/09 20:14
      In Progress In Progress Closed Closed
      13m 45s 1 Howard M. Lewis Ship 24/Mar/09 20:27
      Closed Closed Reopened Reopened
      2d 20h 47m 1 Joachim Van der Auwera 27/Mar/09 17:15
      Reopened Reopened Closed Closed
      19d 22h 45m 1 Joachim Van der Auwera 16/Apr/09 16:00

        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