Closed tresf closed 8 years ago
There was a patch to 2.0 which helped synchronize the sends to avoid the Blocking message pending 10000 for BLOCKING message.
Blocking message pending 10000 for BLOCKING
https://github.com/qzind/tray/commit/a6e71e92dcd46fef40d6e34110a7e3a240e7e4b6
This fix should be evaluated and ported to 1.9 if applicable.
- private static void send(Session session, JSONObject reply) { + private static synchronized void send(Session session, JSONObject reply) { try { session.getRemote().sendString(reply.toString()); } - catch(WebSocketException e) { + catch(Exception e) { log.error("Could not send message", e); } - catch(IOException e) { - log.error("Send failed", e); - } }
Backported in fdbfff48ab4e792a3170fb4b764575788486becf It looks like the catch all block was already there, so this doesn't seem like the cause behind the client needing to reload the software.
Closed via fdbfff4.
There was a patch to 2.0 which helped synchronize the sends to avoid the
Blocking message pending 10000 for BLOCKING
message.https://github.com/qzind/tray/commit/a6e71e92dcd46fef40d6e34110a7e3a240e7e4b6
This fix should be evaluated and ported to 1.9 if applicable.