Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-5546

Websocket endpoint doesn't trigger timeout-uri redirect after desktop timeout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 10.1.0
    • 10.0.0, 10.0.0.FL, 9.6.4
    • None
    • Security Level: Jimmy
    • None

      Steps to Reproduce

      Run a project with zk.xml config:

        <listener>
          <listener-class&amp;amp;gt;org.zkoss.zkmax.au.websocket.WebSocketWebAppInit</listener-class&amp;amp;gt;
        </listener> 
      
        <session-config>
            <max-desktops-per-session>1</max-desktops-per-session>
             <automatic-timeout/>
       <timeout-uri>/timeout.zul</timeout-uri>
        </session-config>
      
      

      Open a tab.

      Open the same page in a different tab.

      Make an action in the first tab (click a button, etc) with an event listener.

      Current Result

      Tab waits on "processing..." forever.

      Expected Result

      Tab redirects to timeout URI

      Debug Information

      If desktop is null, DhtmlUpdateServlet uses wapp.getConfiguration().getTimeoutURI(deviceType) to redirect the page.

      WebsocketEndpoint just returns without redirecting

      Workaround

      attached WebsocketEndpoint.zip
       

            jumperchen jumperchen
            MDuchemin MDuchemin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: