ServerTwoWaySocket accept failure

Classic Servoy
1

I’m using the Updater Plugin and have been able to run some updates without a problem. Recently the server is failing in the communication out to the ftp site and I a getting the following error:

2013-08-26 09:18:35,083 ERROR [2 way Server Acceptor] com.servoy.j2db.util.Debug - ServerTwoWaySocket accept failure
java.net.SocketException: socket closed
at java.net.DualStackPlainSocketImpl.accept0(Native Method)
at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source)
at java.net.AbstractPlainSocketImpl.accept(Unknown Source)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at sun.security.ssl.SSLServerSocketImpl.accept(Unknown Source)
at com.servoy.j2db.rmi.ServerTwoWaySocketFactory$TwoWayServerSocket.run(ServerTwoWaySocketFactory.java:621)
at java.lang.Thread.run(Unknown Source)

This socket close error is new with no changes to the server.
Any ideas to correct this would be greatly appreciated.
Thanks,
Bob

2

how does you setup really work, because this is just an error on the server i guess that’s reporting that a new rmi socket connection is accepted (so a client makes a connection) but then right away it is closed again on the client side.

What does the updater plugin really do? what kind of plugin is that

3

Johan, The Updater Plugin is a plugin that checks to see if an update is available and if so it automatically downloads and installs the updated programming and data as needed. I in the process of testing/implementing this for some on premise clients but in testing my server stopped communicating and I started getting the socket closed error.

more information on the plugin can be found at
https://www.servoyforge.net/projects/servoyupdater/wiki

any idea how to correct the “Closed Socket” error?

4

i have no idea if those are really related at all, because this is not a server problem but a client
a client or what ever outside world thing it also is, makes a connection and then terminates it right away again, maybe it is a plain connection, but it expects a ssl connection i don’t know
On the server you can’t really change, these are just connections that a client drops.

What you can try is to use the Http&Socket Tunnel instead of 2waysocket

5

Thanks Johan,
Changing to http/socket had no effect on the closed socket.

I may need to post this as a questions with the specific Plugin I’m dealing with.

Bob

6

the exception must then be really different, because large piece of that stack that you shown above isn’t there then anymore