o-8443-exec-10: clearHandler (start) 909703826:1000491596
http-nio-8443-exec-10: clearHandler (end)
http-nio-8443-exec-10: onWritePossible (end)
http-nio-8443-exec-10: doWrite (end)
On Fri, Mar 31, 2017 at 9:01 AM, Mark Thomas wrote:
> On 30/03/17 21:13, Robert Lewis wrote:
> > Is
Is there a way to intercept a ping message to send a pong? I need to do
this synchronize sends to the endpoint.
I tried
session.addMessageHandler(new
javax.websocket.MessageHandler.Whole() {
@Override
public void onMessage(PongMessage message) {
Sy
out of the sync block to fix a
deadlock situation indicates otherwise.
Ping on every call fixes the problem for us, and we will be working to move
to 8.5 soon anyway.
Thanks,
-Rob
On Thu, Mar 30, 2017 at 1:09 PM, Mark Thomas wrote:
> On 29/03/17 04:04, Robert Lewis wrote:
> > Thanks
WSS will work if you enable and configure the HTTPS connector in server.xml.
This part of the configuration is not really wss specific and tomcat site
contains a bunch of good docs on how to do this.
> On Mar 29, 2017, at 4:40 PM, Sharat Jagannath wrote:
>
> The code on the tomcat page does no
Rob
On Tue, Mar 28, 2017 at 3:46 PM, Mark Thomas wrote:
> On 28/03/17 00:30, Robert Lewis wrote:
> > Hi,
> >
> > I am tracking down a fairly sporadic bug in our software that uses Tomcat
> > 8.0.38. Long story short, sometimes calls to Basic.sendBinary() to a full
&g
Hi,
I am tracking down a fairly sporadic bug in our software that uses Tomcat
8.0.38. Long story short, sometimes calls to Basic.sendBinary() to a full
buffer then to a small buffer (eg. 8192x3 then 444 bytes). The first 8192
sends will succeed and occasionally we see the last 444 byte send 'fail'
Hi,
I am tracking down a fairly sporadic bug in our software that uses Tomcat
8.0.38. Long story short, sometimes calls to Basic.sendBinary() to a full
buffer then to a small buffer (eg. 8192x3 then 444 bytes). The first 8192
sends will succeed and occasionally we see the last 444 byte send 'fail'
