Servoy Client (3.5.6 Win) Freezing...

Classic Servoy
1

We have about 20 clients on Win XP and Vista connecting to Server running on Mac OS X.
All clients work fine except one.
This last client freezes about 10 times a day and the user has to force quit and restart.
We see lots of messages in the log, similar to the ones below:

2008-10-07 17:06	TaskExecuter[10]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.ConnectIOException: Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: SocketPool is closed
2008-10-07 17:06	TaskExecuter[10]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 40a56857-e24e-4e14-a8a1-44a7aeab42ff, Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: SocketPool is closed
2008-10-07 17:06	ClientExportNotifyListner[278]	ERROR	com.servoy.j2db.util.Debug	Signalling channel lost when reading pings or client export notifies, removing ports: [3476]
java.net.SocketException: Operation timed out 
    	at java.net.SocketInputStream.socketRead0(Native Method) 
    	at java.net.SocketInputStream.read(SocketInputStream.java:129) 
    	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) 
    	at java.io.BufferedInputStream.read(BufferedInputStream.java:235) 
    	at java.io.DataInputStream.readInt(DataInputStream.java:353) 
    	at com.servoy.j2db.util.rmi.d$1.run(Unknown Source)
2008-10-07 17:06	ClientExportNotifyListner[278]	ERROR	com.servoy.j2db.util.Debug	Signalling channel lost, removing ports: [3476]
java.net.SocketException: Operation timed out 
    	at java.net.SocketInputStream.socketRead0(Native Method) 
    	at java.net.SocketInputStream.read(SocketInputStream.java:129) 
    	at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) 
    	at java.io.BufferedInputStream.read(BufferedInputStream.java:235) 
    	at java.io.DataInputStream.readInt(DataInputStream.java:353) 
    	at com.servoy.j2db.util.rmi.d$1.run(Unknown Source)
2008-10-07 17:05	TaskExecuter[15]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.ConnectIOException: Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:05	TaskExecuter[15]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 40a56857-e24e-4e14-a8a1-44a7aeab42ff, Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:04	TaskExecuter[10]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.ConnectIOException: Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:04	TaskExecuter[10]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 40a56857-e24e-4e14-a8a1-44a7aeab42ff, Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:03	TaskExecuter[14]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.ConnectIOException: Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:03	TaskExecuter[14]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 40a56857-e24e-4e14-a8a1-44a7aeab42ff, Exception creating connection to: 10.49.162.245; nested exception is: java.io.InterruptedIOException: The socket pool for a client 10.49.162.245:3476 did not recieve a callback socket from the client within 60002ms, pool still empty
2008-10-07 17:01	TaskExecuter[19]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Operation timed out
2008-10-07 17:01	TaskExecuter[19]	ERROR	com.servoy.j2db.dataprocessing.ClientManager	Error flushing message buffer to client 40a56857-e24e-4e14-a8a1-44a7aeab42ff, Error unmarshaling return header; nested exception is: java.net.SocketException: Operation timed out

Any ideas? Is this a computer, network or Servoy problem?

2

I had the same issue today with 4 clients where one client was freezing (4 times, also 3.5.6)

that’s the only one, using Windows Vista, all connecting from the same LAN (no WAN)

the strange thing from what I saw that all the clients showed a nice ip-address: 192.168.2.x
but the problematic client showed: 169.254.x.x (in the admin-pages)

I had to restart the servoy server, to force quit the session of this client in the server also
(normal quiting, in the servoy admin-page was not possible)

after the server restart, the client connecting fine again, but still showed the strange ip-adres.

3

the problem is that the client somehow doesnt talk to the server when the server wants to.

What you could use is the http tunnel and see if that helps

What are the exact network settings you now have?

4

harjo: does that pc with that strange network address somehow has 2 network cards?

5

I don’t know yet, I have an appointment there next week!