We resolved this issue by calling removeCallback() and calling onTimeout() on that callback instead of the passed in one. This will be null if it has already been cancelled. Otherwise it would call .onTimeout() on a callback that was cancelled or already timed out (potentially).
We had it happen and traced the issue back. Edited our branch appropriately.
mrniko
commented
10 years ago
We resolved this issue by calling removeCallback() and calling onTimeout() on that callback instead of the passed in one. This will be null if it has already been cancelled. Otherwise it would call .onTimeout() on a callback that was cancelled or already timed out (potentially).
We had it happen and traced the issue back. Edited our branch appropriately.
https://github.com/Zipwhip/netty-socketio/commit/12aa05292370fcf6377679b880fbffda6748fc3d