Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13941

Failed to persist session attribute with Websocket endpoints

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 13.0.0.Final
    • Web Sockets
    • None
    • Hide
      1. Add the following configuration to your standalone.xml
         <servlet-container name="default">
        <jsp-config/>
        <persistent-sessions path="session" relative-to="jboss.server.temp.dir"/>
        <websockets/>
        </servlet-container>
      2. Deploy the attached war
      3. Go to http://localhost/index.jsp to create a websocket session
      4. Try reloading the deployment. You should be able to see the exception
      Show
      Add the following configuration to your standalone.xml  <servlet-container name="default"> <jsp-config/> <persistent-sessions path="session" relative-to="jboss.server.temp.dir"/> <websockets/> </servlet-container> Deploy the attached war Go to http://localhost/index.jsp  to create a websocket session Try reloading the deployment. You should be able to see the exception
    • User Experience
    • Undefined
    • ---
    • ---

      When WildFly is configured to persist sessions (standalone mode) during restart/redeploy and contains a websocket endpoint, a NotSerializableException is thrown:

      Failed to persist session attribute io.undertow.websocket.current-connections with value [WebSocket13Channel peer /127.0.0.1:64853 local /127.0.0.1:8080[ No Receiver [] – [] – []]] for session xxxxxxxx: java.io.NotSerializableException: io.undertow.websockets.core.protocol.version13.WebSocket13Channel

       

      This start to happen in wildfly 13. The deployment works fine in wildfly 12.

              parsharm Parul Sharma
              mas.ahmad Abi Sarwan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: