legalStateException(e);
}
}
}
private class SemaphoreSendHandler implements SendHandler {
private final Semaphore semaphore;
private SemaphoreSendHandler(Semaphore semaphore) {
this.semaphore = semaphore;
}
ected diff < 60ms but was [65475211], count [960]
Expected diff > 40ms but was [35346555], count [962]
So the delay is at most 2 milliseconds, which is acceptable.
I think that you understood my problem quite well. It seems that the problem
can't be reproduced in this test.
I also tried a
On 07/03/17 14:55, Mark Thomas wrote:
> On 07/03/17 11:03, Mark Thomas wrote:
>> On 07/03/17 08:28, Pesonen, Harri wrote:
>>> Hello, we have a problem that Tomcat WebSocket does not always send
>>> asynchronous messages. This problem is random, and it has been reproduc
On 07/03/17 11:03, Mark Thomas wrote:
> On 07/03/17 08:28, Pesonen, Harri wrote:
>> Hello, we have a problem that Tomcat WebSocket does not always send
>> asynchronous messages. This problem is random, and it has been reproduced in
>> Tomcat 8.5.6 and 8.5.11. Synchronized
On 07/03/17 08:28, Pesonen, Harri wrote:
> Hello, we have a problem that Tomcat WebSocket does not always send
> asynchronous messages. This problem is random, and it has been reproduced in
> Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, and also the
> asynchronous ope
Hello, we have a problem that Tomcat WebSocket does not always send
asynchronous messages. This problem is random, and it has been reproduced in
Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, and also the
asynchronous operations work except in one special case. When there is a big