Persistent Sessions bug? Failed to persist sessions: NotSerializableException

[zeus3324]

Version: WildFly-8.1.0-Final

I have configured my standalone.xml to use persistence sessions on redeploy. When ever I redeploy I get the errors below relating to persistence sessions. Here is the line I have added to my standalone.xml:

<servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only">

    <jsp-config/>

    <persistent-sessions path="session" relative-to="jboss.server.temp.dir"/>

</servlet-container>

This is the error upon saving the session upon undeploy:

15:59:19,459 WARN  [io.undertow.servlet] (MSC service thread 1-10) UT015010: Failed to persist sessions: java.io.NotSerializableException: org.wildfly.extension.undertow.AbstractPersistentSessionManager$SessionEntry

  at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:894)

  at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:683)

  at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)

  at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:115)

  at org.wildfly.extension.undertow.DiskBasedModularPersistentSessionManager.persistSerializedSessions(DiskBasedModularPersistentSessionManager.java:72)

  at org.wildfly.extension.undertow.AbstractPersistentSessionManager.persistSessions(AbstractPersistentSessionManager.java:63)

  at io.undertow.servlet.handlers.SessionRestoringHandler.stop(SessionRestoringHandler.java:90) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]

  at io.undertow.servlet.core.DeploymentManagerImpl.stop(DeploymentManagerImpl.java:512) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]

  at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:113)

  at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100)

  at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)

  at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]

  at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

Caused by: an exception which occurred:

  in object java.util.HashMap@b0096a85

Obviously then this error occurs when redeploying, due to the one above.

15:03:04,766 WARN  [io.undertow.servlet] (MSC service thread 1-11) UT015008: Failed to load development mode persistent sessions: java.io.EOFException: Read past end of file

  at org.jboss.marshalling.SimpleDataInput.eofOnRead(SimpleDataInput.java:155)

  at org.jboss.marshalling.SimpleDataInput.readUnsignedByteDirect(SimpleDataInput.java:298)

  at org.jboss.marshalling.SimpleDataInput.readUnsignedByte(SimpleDataInput.java:253)

  at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:213)

  at org.jboss.marshalling.river.RiverUnmarshaller.doReadMapObject(RiverUnmarshaller.java:199)

  at org.jboss.marshalling.river.RiverUnmarshaller.readMapData(RiverUnmarshaller.java:823)

  at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:686)

  at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:213)

  at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:45)

  at org.wildfly.extension.undertow.DiskBasedModularPersistentSessionManager.loadSerializedSessions(DiskBasedModularPersistentSessionManager.java:94)

  at org.wildfly.extension.undertow.AbstractPersistentSessionManager.loadSessionAttributes(AbstractPersistentSessionManager.java:83)

  at io.undertow.servlet.handlers.SessionRestoringHandler.start(SessionRestoringHandler.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]

  at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:476) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]

  at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)

  at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)

  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]

  at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

Caused by: an exception which occurred:

  in map value at index [0] of size [1]

[smarlow]

I don't get very much out of the above error exception.  Perhaps your application code is putting an object into the WEB session that is not Serializable.  I'm not sure if there are any TRACE log settings that would show more information.

You could run the application server in a debugger and catch the java.io.NotSerializableException and see if you can view the map values to see what the actual object in question is.  That might be helpful. 

[ctomc]

Persistent session manager is not 100% stable yet that is also reason why it is not enabled by default.

But any testing is useful as it can provide us with more chance to fix all scenarios.

Can you create jira WildFly - JBoss Issue Tracker with some simple reproducer so it will be easier for us to fix it.

Thank you.

[pferraro]

You can also achieve <persistent-session/> behavior by adding <distributable/> to your web.xml.  When using a non-ha profile (e.g. standalone.xml), this enables session passivation - and, by JEE specification contract, requires your session attributes to be serializable.  By default, the session passivation threshold is infinite (meaning, the server will retain *all* sessions in memory), thus sessions will only passivate upon undeploy/shutdown, and activate upon redeploy/startup.

[zeus3324]

I have a feeling that we may be adding something to the HttpSession that is not serializable. I will try to deploy a different application to try to narrow down the cause, and then post the results.

[zeus3324]

I did try with a simple application where there is definitely no adding of anything to the session. The session is the vanilla session created by WildFly. The error still occurs.

Issue logged here: https://issues.jboss.org/browse/WFLY-3576

This has been fixed in 8.2.0.CR1