Strange error running a relatively long process

Classic Servoy
1

Hi All

I get errrors I can’t interpret when running a relatively long running process (~1 hour). It is reproducable. The relevant part of the code in the method is embedded in a transaction. This is what I get (attached also as screenshot):

2012-10-15 10:50:43,527 ERROR [multiplexer-reader-16818e17[SSL_NULL_WITH_NULL_NULL: Socket[addr=/<ip-addr>,port=49223,localport=1099]]] com.sebster.tunnel.impl.sd - multiplexer failed for client 017fda8e-1bbe-45fd-b93f-a3371f233fa2
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.kd.c(kd.java:54)
	at com.sebster.tunnel.impl.md.run(md.java:10)
	at java.lang.Thread.run(Unknown Source)
2012-10-15 10:54:30,308 ERROR [TaskExecuter[0]] com.servoy.j2db.dataprocessing.Zb - Error flushing message buffer to client B566B24C-E7CC-4FEE-BA36-5864F8CDC564
java.rmi.ConnectException: Connection refused to host: <ip-addr>; nested exception is: 
	java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	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 $Proxy13.isAlive(Unknown Source)
	at com.servoy.j2db.dataprocessing.ClientProxy.Zc(ClientProxy.java:131)
	at com.servoy.j2db.dataprocessing.Zo.run(Zo.java:15)
	at com.servoy.j2db.util.TaskExecuter.run(TaskExecuter.java:82)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	at com.sebster.tunnel.impl.me.createSocket(me.java:14)
	at com.servoy.j2db.server.rmi.tunnel.WrappingCompressingRMIClientSocketFactory.createSocket(WrappingCompressingRMIClientSocketFactory.java:28)
	... 11 more
2012-10-15 10:54:40,308 ERROR [TaskExecuter[1]] com.servoy.j2db.dataprocessing.Zb - Error flushing message buffer to client B566B24C-E7CC-4FEE-BA36-5864F8CDC564
java.rmi.ConnectException: Connection refused to host: <ip-addr>; nested exception is: 
	java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	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 $Proxy13.isAlive(Unknown Source)
	at com.servoy.j2db.dataprocessing.ClientProxy.Zc(ClientProxy.java:131)
	at com.servoy.j2db.dataprocessing.Zo.run(Zo.java:15)
	at com.servoy.j2db.util.TaskExecuter.run(TaskExecuter.java:82)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	at com.sebster.tunnel.impl.me.createSocket(me.java:14)
	at com.servoy.j2db.server.rmi.tunnel.WrappingCompressingRMIClientSocketFactory.createSocket(WrappingCompressingRMIClientSocketFactory.java:28)
	... 11 more
2012-10-15 10:54:50,308 ERROR [TaskExecuter[0]] com.servoy.j2db.dataprocessing.Zb - Error flushing message buffer to client B566B24C-E7CC-4FEE-BA36-5864F8CDC564
java.rmi.ConnectException: Connection refused to host: <ip-addr>; nested exception is: 
	java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	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 $Proxy13.isAlive(Unknown Source)
	at com.servoy.j2db.dataprocessing.ClientProxy.Zc(ClientProxy.java:131)
	at com.servoy.j2db.dataprocessing.Zo.run(Zo.java:15)
	at com.servoy.j2db.util.TaskExecuter.run(TaskExecuter.java:82)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: no multiplexer found for server with id=017fda8e-1bbe-45fd-b93f-a3371f233fa2
	at com.sebster.tunnel.impl.me.createSocket(me.java:14)
	at com.servoy.j2db.server.rmi.tunnel.WrappingCompressingRMIClientSocketFactory.createSocket(WrappingCompressingRMIClientSocketFactory.java:28)
	... 11 more

Any idea what that means and what that I/O error in the screenshot means? I am stuck as I don’t know what this error messages mean.

Regards, Robert

app error.png
app error.png428×109 15.2 KB

io and other errors.png
io and other errors.png914×350 15.5 KB

2

Robert,

The smart client was somehow disconnected from the server and managed to reconnect.
Because of the transactions, the client could not just continue with what it was doing, so it needs to restart the solution, that is what the dialog tries to say.

Rob

3

Hi Rob

Thanks for clarifying. This error (up to now) only occurs when executing this long running process. I read in the forum about similar or same failures, but they are quite old. There are suggestions about query validation setting to SELECT 1 or ApplicationServer.pingDelay to a low value, e. g. 50. Are these tips still valid, i. e. should I play with them or are they a thing of the past?

Regards, Robert

rgansevles:
Robert,

The smart client was somehow disconnected from the server and managed to reconnect.
Because of the transactions, the client could not just continue with what it was doing, so it needs to restart the solution, that is what the dialog tries to say.

Rob