4 Replies Latest reply on Oct 8, 2011 4:33 PM by Pol Patric

    Disconnected browser causes Errai to repeatively throws QueueUnavailableException

    Melvin Ramos Newbie



      So I have a code that issues a subscription from the GWT client, and the server creates a conversation with the client with replyRepeating every 2 seconds, thus creating a HTTP Streaming.


      I'm guessing because the browser had been disconnected, either by closing the browser or network failure, the server should kill the worker threads for that specific client?


      I don't know if GrizzlyCometServlet or DefaultBlockingQueue has way to do that.



      org.jboss.errai.bus.server.QueueUnavailableException: no queue available to send. (queue or session may have expired)

      at org.jboss.errai.bus.server.ServerMessageBusImpl.getQueueByMessage(ServerMessageBusImpl.java:882)

        at org.jboss.errai.bus.server.ServerMessageBusImpl.send(ServerMessageBusImpl.java:412)

      at org.jboss.errai.bus.server.Worker.deliverToBus(Worker.java:143)

      at org.jboss.errai.bus.server.Worker.run(Worker.java:111)