2 Replies Latest reply on Dec 3, 2005 3:27 PM by ereze

    Subject not removed on session invalidation 3.2.7

    ereze

      I am moving to 3.2.7 from 3.2.6. Problem is that when my application is calling session.invalidate() for some reason the application seem to think that the user is still logged in. Has that anything to do with the subject being saved? or that new flag flushOnSessionInvalidation?

      Since I am using XDoclet to generate the Jboss-web.xml and XDoclet still doesn't support this new flag, I guess I am stuck and need to stay with 3.2.6 for now.

      Thanks in advance,

      Erez

        • 1. Re: Subject not removed on session invalidation 3.2.7
          starksm64

          Until your in a new request there can be state outside of the session that is still seen in the current request.

          • 2. Re: Subject not removed on session invalidation 3.2.7
            ereze

            In fact,

            I dumped the XDoclet and written the jboss-web manually and inserted the flushOnSessionInvalidation flag. It works fine.

            The initial reason I moved to the 3.2.7 was that I read somewhere that maybe 3.2.7 solved a problem scheduling services not finding the scheduled class after a redeployment of the application EAR.
            The scheduler still (in 3.2.7 too) does not find the scheduled class after the redeployment.

            Can you give me any pointers or any solution?

            Thanks,

            -- Erez