"Could not deserialize session data" error during shutdown WLS 6.0SP2

Question

          Hello all,
          I get this Error ("Could not deserialize session data") when shutting down WLS
          6.0 SP2.
          I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to use memory-based
          storage for session data. So WLS should not try to serialize the session and save
          it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          methods and realized that WLS calls writeObject on all in the session saved objects
          and readObject directly afterwards. Here's the stackTrace:
          ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          AttributeWrapper.getObject()
          SessionData.removeAttribute()
          SessionData.removeValue()
          SessionData.remove()
          MemorySessionContext.invalidateSession()
          MemorySessionContext.shutDown()
          WebAppServletContext.destroyServlets()
          HttpServer.destroyServlets()
          HttpServer.shutDown()
          WebService.shutDown()
          ServerServiceList.shutDown()
          T3srvr.die()
          T3srvr.waitForDeath()
          T3srvr.run()
          Server.main()
          I do save some objects which are not Serializable in the session. I understand
          that session data can be made persistent in a file/jdbc and then the objects must
          be Serializable but not when saving the session data in memory.
          Why is WLS trying to Serialize the Session Data and how can I switch it off ?
          The Documentation says that it is allowed to store any object in the sessio, as
          long as it is not persistet.
          Thanks for your help,
          Oliver
          [weblogic.xml]
          

Answer 1

          Hello Oliver & All-
          Did anyone ever make any progress with this question, or come up with an answer?
          I've found similar behavior when properly shuting down a WLS server with this command:
          java -classpath $CLASSPATH weblogic.Admin -url t3://localhost:7001 -username <user>
          -password <passwd> SHUTDOWN
          TIA.
          --oliver.
          "Oliver Seiler" <[email protected]> wrote:
          >
          >Hello all,
          >
          >I get this Error ("Could not deserialize session data") when shutting down
          >WLS
          >6.0 SP2.
          >I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to
          >use memory-based
          >storage for session data. So WLS should not try to serialize the session
          >and save
          >it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
          >methods and realized that WLS calls writeObject on all in the session saved
          >objects
          >and readObject directly afterwards. Here's the stackTrace:
          >
          >ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
          >AttributeWrapper.getObject()
          >SessionData.removeAttribute()
          >SessionData.removeValue()
          >SessionData.remove()
          >MemorySessionContext.invalidateSession()
          >MemorySessionContext.shutDown()
          >WebAppServletContext.destroyServlets()
          >HttpServer.destroyServlets()
          >HttpServer.shutDown()
          >WebService.shutDown()
          >ServerServiceList.shutDown()
          >T3srvr.die()
          >T3srvr.waitForDeath()
          >T3srvr.run()
          >Server.main()
          >
          >I do save some objects which are not Serializable in the session. I understand
          >that session data can be made persistent in a file/jdbc and then the objects
          >must
          >be Serializable but not when saving the session data in memory.
          >Why is WLS trying to Serialize the Session Data and how can I switch it
          >off ?
          >The Documentation says that it is allowed to store any object in the sessio,
          >as
          >long as it is not persistet.
          >
          >Thanks for your help,
          > Oliver
          >