Connection refused in the server log

Classic Servoy
1 
TaskExecuter[1]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.ConnectException: Connection refused to host: 192.168.2.115; nested exception is: java.net.ConnectException: Connection refused: connect
2007-07-09 11:33	TaskExecuter[1]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 2134c8e3-230a-4043-acc4-40a339ab953b, Connection refused to host: 192.168.2.115; nested exception is: java.net.ConnectException: Connection refused: connect
2007-07-09 11:33	TaskExecuter[15]	ERROR	com.servoy.j2db.dataprocessing.ClientManager java.rmi.ConnectException: Connection refused to host: 192.168.2.115; nested exception is: java.net.ConnectException: Connection refused: connect
2007-07-09 11:33	TaskExecuter[15]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 2134c8e3-230a-4043-acc4-40a339ab953b, Connection refused to host: 192.168.2.115; nested exception is: java.net.ConnectException: Connection refused: connect

We are getting these intermittently. Our suspicion is that the router or Windows is causing this, but we don’t know were to look to fix this.

192.168.2.115 is a client IP.
Windows XP client
Java version 5.10.

Server:
JDK Information
java.vm.name=Java HotSpot™ Client VM
java.vm.version=1.6.0_01-b06
java.vm.info=mixed mode, sharing
java.vm.vendor=Sun Microsystems Inc.

Operating System Information
os.name=Windows 2003
os.version=5.2
os.arch=x86

rmi.connection.timeout: 120
ApplicationServer.pingDelay: 60
SocketFactory.useTwoWaySocket: Yes

Ay ideas?

2

you could get this error when a client doesn’t disconnect correctly. For example of a crash or a kill. But also when you have a client open and you suspend/hibernate your laptop.

So it doesn’t have to mean that it is a real problem. Do you have problems with some clients?

3

Yes, we have some infrequent intermittent ‘weird-and-wonderful’ errors, such as trying to print an invoice, and Servoy printing the wrong invoice, having failied to load the correct data before printing…

This particuar error only happens about once a month to a WAN-client…

192.168.2.115, the client the example above is on the LAN.