Dear Servoy Gurus,
we have a 60+ concurrent client servoy server behind our internet
connection and a new firewall setup.
On the client side we encounter enormuous delays (up to 4 to 5 minutes per click!!)
when using this setup.
The servoy server log shows “Signalling lost”, “ServerTwoSocket accept failure”
and “Error flushing message buffer to client 4213c158-fffa-11dc-b1cd-a0136e9f1c92, Connection refused to host: 192.168.1.77; nested exception is: java.net.ConnectException: Connection timed out” messages.
This looks like connections from the server to the client not being build up successfully.
Please note the server log pasted below.
Do you have any hints on how servoy reacts to high latency client connections?
Could it be that many such connections could cause the complete server to slow
down?
I’d kindly appreciate any pointers.
Thank you,
Michael Wirz
2008-04-01 15:49:56 : Signalling channel lost when reading pings or client export notifies, removing ports: [2001]
2008-04-01 15:49:56 : Signalling channel lost when reading pings or client export notifies, removing ports: [2014]
2008-04-01 15:50:05 : Signalling channel lost when reading pings or client export notifies, removing ports: [2024]
2008-04-01 15:50:06 : Signalling channel lost when reading pings or client export notifies, removing ports: [2009]
2008-04-01 15:50:07 : Signalling channel lost when reading pings or client export notifies, removing ports: [2011]
2008-04-01 15:50:09 : ServerTwoWaySocket accept failure
2008-04-01 15:50:13 : ServerTwoWaySocket accept failure
2008-04-01 15:50:13 : ServerTwoWaySocket accept failure
2008-04-01 15:50:13 : Signalling channel lost when reading pings or client export notifies, removing ports: [2028]
2008-04-01 15:50:17 : ServerTwoWaySocket accept failure
2008-04-01 15:50:19 : ServerTwoWaySocket accept failure
2008-04-01 15:50:19 : ServerTwoWaySocket accept failure
2008-04-01 15:50:31 : ServerTwoWaySocket accept failure
2008-04-01 15:50:32 : ServerTwoWaySocket accept failure
2008-04-01 15:50:32 : ServerTwoWaySocket accept failure
2008-04-01 15:50:38 : ServerTwoWaySocket accept failure
2008-04-01 15:50:40 : Signalling channel lost when reading pings or client export notifies, removing ports: [2032]
2008-04-01 15:50:41 : ServerTwoWaySocket accept failure
2008-04-01 15:50:57 : Signalling channel lost when reading pings or client export notifies, removing ports: [2035]
2008-04-01 15:51:00 : Signalling channel lost when reading pings or client export notifies, removing ports: [2002]
2008-04-01 15:51:05 : Signalling channel lost when reading pings or client export notifies, removing ports: [2023]
2008-04-01 15:51:07 : ServerTwoWaySocket accept failure
2008-04-01 15:51:07 : ServerTwoWaySocket accept failure
2008-04-01 15:51:07 : Signalling channel lost when reading pings or client export notifies, removing ports: [2006]
2008-04-01 15:51:07 : ServerTwoWaySocket accept failure
2008-04-01 15:51:08 : ServerTwoWaySocket accept failure
2008-04-01 15:51:14 : ServerTwoWaySocket accept failure
2008-04-01 15:51:18 : Signalling channel lost when reading pings or client export notifies, removing ports: [2038]
2008-04-01 15:51:18 : ServerTwoWaySocket accept failure
2008-04-01 15:51:18 : ServerTwoWaySocket accept failure
2008-04-01 15:51:30 : Signalling channel lost when reading pings or client export notifies, removing ports: [2039]
2008-04-01 15:51:35 : ServerTwoWaySocket accept failure
2008-04-01 15:51:44 : ServerTwoWaySocket accept failure
2008-04-01 15:52:23 : Signalling channel lost when reading pings or client export notifies, removing ports: [2004]
2008-04-01 15:52:47 : Signalling channel lost when reading pings or client export notifies, removing ports:
2008-04-01 15:52:52 : Signalling channel lost when reading pings or client export notifies, removing ports: [2036]
2008-04-01 16:50:38 : Signalling channel lost when reading pings or client export notifies, removing ports: [2098]
2008-04-01 16:51:32 : Error flushing message buffer to client 06a87027-fff3-11dc-b1cd-a0136e9f1c92, Connection refused to host: 192.168.1.77; nested exception is: java.net.ConnectException: Connection timed out
2008-04-01 16:53:03 : Error flushing message buffer to client 84fad4ac-fffa-11dc-b1cd-a0136e9f1c92, Exception creating connection to: 192.168.1.124; nested exception is: java.io.InterruptedIOException: SocketPool is closed
2008-04-01 16:53:04 : ServerTwoWaySocket accept failure
2008-04-01 16:53:55 : Error flushing message buffer to client 4213c158-fffa-11dc-b1cd-a0136e9f1c92, Connection refused to host: 192.168.1.77; nested exception is: java.net.ConnectException: Connection timed out
2008-04-01 16:57:04 : Error flushing message buffer to client 4213c158-fffa-11dc-b1cd-a0136e9f1c92, Connection refused to host: 192.168.1.77; nested exception is: java.net.ConnectException: Connection timed out