B4J Question error websocket push notification

Roberto P.

Well-Known Member
Licensed User
Longtime User
in my project I used the example of push notification. The project works for about a year without any problems. A few days ago I compartment this error and I can not figure out where it came from.


java.io.EOFException: Connection has been closed locally
at org.eclipse.jetty.websocket.common.io.FrameFlusher.enqueue(FrameFlusher.java:338)
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.outgoingFrame(AbstractWebSocketConnection.java:598)
at org.eclipse.jetty.websocket.common.extensions.ExtensionStack$Flusher.process(ExtensionStack.java:389)
at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:241)
at org.eclipse.jetty.util.IteratingCallback.succeeded(IteratingCallback.java:365)
at org.eclipse.jetty.websocket.common.extensions.ExtensionStack$Flusher.writeFailed(ExtensionStack.java:425)
at org.eclipse.jetty.websocket.common.io.FrameFlusher.notifyCallbackFailure(FrameFlusher.java:390)
at org.eclipse.jetty.websocket.common.io.FrameFlusher$Flusher.onCompleteFailure(FrameFlusher.java:103)
at org.eclipse.jetty.util.IteratingCallback.failed(IteratingCallback.java:401)
at org.eclipse.jetty.io.WriteFlusher$PendingState.fail(WriteFlusher.java:260)
at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:401)
at org.eclipse.jetty.io.SelectChannelEndPoint$3.run(SelectChannelEndPoint.java:89)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
at java.lang.Thread.run(Thread.java:745)

Version B4J: 4.7

In the client App, show this error:
WebSocket Closed....: WebSockets protocol violation

thank you and greetings
 
Last edited:

Roberto P.

Well-Known Member
Licensed User
Longtime User
I SOLVED.
this error occurs when there is too much data to be sent with notifications.
thank you
 
Upvote 0
Top