3 Replies Latest reply on Jul 26, 2014 12:05 AM by Harit Himanshu

    JavaEE Websocket: closing browser tab closes all sessions irrespective of browser?

    Harit Himanshu Newbie

      I have a websocket endpoint as


      public class TweetStreamServer {

          private static final Logger LOGGER = LoggerFactory.getLogger(TweetStreamServer.class);




          public void tweets(final String message, final Session session) throws IOException, InterruptedException {

              System.out.println("session id:" + session.getId() + ", search term: " + message);

              final Client twitterClient = TwitterHoseBird.getInstance(message);

              while (!session.getOpenSessions().isEmpty()) {

                  for (final Session s : session.getOpenSessions()) {

                      if (twitterClient.isDone()) {

                          System.out.println("Twitter Client Done, waiting ...");







      I deploy this on WildFly 8.1.0 Final. Then I open multiple tabs on Chrome, Safari and run the following

      var connection = new WebSocket('ws://');

      connection.onopen = function () {



      connection.onerror = function (error) {

        console.log('WebSocket Error ' + error);


      connection.onmessage = function (e) {

        console.log('Server: ' + e.data);


      connection.onclose = function (e) {

        console.log('closing session');


      • Then when I do connection.close(); on one of the tabs, only that connection breaks while all the other tabs are still receiving the data
      • But if I close one of the tabs (in any browser), all the sessions that were open in all the other tabs close session with closing session message

      - Is it not a valid use case that if user closes a tab in one browser, all the other tabs should still receive the data?
      - Do you see any bug/issue with what I am doing?
      - How can I fix this issue?

      P.S: I asked this question on StackOverflow, but arungupta, recommended me to ask this question here.

      Please help me understand the behavior. As far as I test, I see this as bug, but can't assert since I do not have much idea


      Thank you