Error flushing message buffer to client..
Posted:
Mon Jan 08, 2018 1:59 pmby satya.sahu
Hi
My solution is running with Servoy version 7.4.3 -releaseNumber 2036 on MAC.
I got the below error on servoy admin(basically while doing any flush)
- Code: Select all
om.servoy.j2db.server.dataprocessing.Zb Error flushing message buffer to client 99E2D92A-7EC1-41B5-984E-8D5EEF13B001
java.lang.NullPointerException
at com.servoy.j2db.ClientStub.closeSolution(ClientStub.java:89)
at com.servoy.j2db.server.dataprocessing.ClientProxy.Zc(ClientProxy.java:118)
at com.servoy.j2db.server.dataprocessing.Zo.run(Zo.java:18)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Kindly share any solution.
Thanks
Satya
Re: Error flushing message buffer to client..
Posted:
Wed Jan 10, 2018 11:50 amby LXS
I see similar messages in the servoy admin log:
Error flushing message buffer to client XXXXXX
java.rmi.ConnectException: Connection refused to host: 192.168.1.1; nested exception is:
java.net.ConnectException: no multiplexer found for server with id=YYYYYYYYYY
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown Source)
at java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source)
at com.sun.proxy.$Proxy24.notifyDataChange(Unknown Source)
at com.servoy.j2db.server.dataprocessing.ClientProxy.Zc(ClientProxy.java:73)
at com.servoy.j2db.server.dataprocessing.Zo.run(Zo.java:13)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: no multiplexer found for server with id=YYYYYYYYYY
at com.sebster.tunnel.impl.hd.createSocket(hd.java:12)
at com.servoy.j2db.server.rmi.tunnel.WrappingCompressingRMIClientSocketFactory.createSocket(WrappingCompressingRMIClientSocketFactory.java:28)
... 12 more
multiplexer failed for client c2777f89-947b-4327-948d-b08c2075e4b1
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source)
at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
at com.sebster.tunnel.impl.xd.e(xd.java:39)
at com.sebster.tunnel.impl.lc.run(lc.java:18)
at java.lang.Thread.run(Unknown Source)
Re: Error flushing message buffer to client..
Posted:
Thu Jan 11, 2018 7:37 amby satya.sahu
Hi
Is there any solution of this issue? Please help.
Thanks
Satya
Re: Error flushing message buffer to client..
Posted:
Wed Jan 17, 2018 2:16 pmby jcompagner
they are really not simular
the null pointer exception should be fixed in later releases that code has checks and other improvements around that area.
the connection refused/timeouts are really network problems, the server can't reach the client anymore, it will try to get to it a few times and then clean it up.
There is no solution from servoy side, except ignoring those exceptions. Or trying to look if there are network problems in the middle
But this can also happen for example if a laptop has a smart client open and then closes the lid (let it go into suspend)