javaeetutorial
  1. javaeetutorial
  2. JAVAEETUTORIAL-258

Websocket dukeetf2 and websocketbot, socket remains open after browser tab closed

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Works as designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: examples
    • Labels:
      None
    • Environment:

      Chrome Version 32.0.1700.77 GlassFish Server Open Source Edition 4.0 (build 89) OSX 10.9.1

      Description

      In the dukeetf2 websocket example:

      Why does the server keep sending the messages after the browser tab on the client is closed? Why is the ETFEndpoint @OnClose never called? I understand that the timer service keeps hitting send every second, but the connection should be closed surely, and its session removed from the queue? After which the queue should be empty?

      The websocketbot application also does the same, it does not close the connections, from both Chrome and Safari, neither closing the tabs nor the browser works on my machine

        Activity

        pggeldenhuys created issue -
        Hide
        jendrock added a comment -

        Closing the browser tab does not undeploy the application. If you undeploy the example, the socket closes and the issue no longer exists.

        Show
        jendrock added a comment - Closing the browser tab does not undeploy the application. If you undeploy the example, the socket closes and the issue no longer exists.
        jendrock made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Works as designed [ 7 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            pggeldenhuys
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: