Messages beyond first one are serialized but not flushed about engine.io-client-java HOT 3 CLOSED

In the Polling transport's write method, the transport is set to read-only with this.writable = false;. A callback callbackfn is defined which is meant to switch back to read-write.

The callbackfn is passed to self.doWrite() as fn, and it's supposed to be called on Request.EVENT_SUCCESS. And it appears to be:

EventThread.exec(new Runnable() {
    @Override
    public void run() {
        fn.run();
    }
});

However, this does not work.

from engine.io-client-java.

The EventThread is being blocked by polling: PollingXHR.doPoll()'s handler for Request.EVENT_DATA events calls Polling._onData() on the EventThread, which gets stuck.

from engine.io-client-java.

Resolved. This was an issue in client code. Essentially, a handler for an message type or event can block itself if it tries to emit a message but doesn't return.

from engine.io-client-java.