However, there is one distinct difference, essentially we freeze everyday. I have to restart the server in the middle of the day.
This has been going on almost since the first day we moved to 3.5.x which was almost seven weeks ago. The users are more than frustrated, to point where less and less of them are using Servoy everyday and more are reverting back to email and spreadsheets to get their work done.
I have 65 licenses and I’m lucky if I get 16 users on the system now.
This as to be fixed!
If moving back to 2.2.8 is going to give us relief yet limit our functionality, so be it, as soon I will be the only one left using the product.
Servoy 3.5.7
Java Version 6 Update 11
Here are the kinds of errors I’m getting:
java.net.SocketException: Connection reset
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 java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.DataInputStream.readInt(Unknown Source)
at com.servoy.j2db.util.rmi.d$1.run(Unknown Source)
2009-01-07 14:02 ClientExportNotifyListner[74] ERROR com.servoy.j2db.util.Debug Signalling channel lost, removing ports: [3076]
java.net.SocketException: Connection reset
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 java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.DataInputStream.readInt(Unknown Source)
at com.servoy.j2db.util.rmi.d$1.run(Unknown Source)
2009-01-07 14:02 SocketAccepter[10] ERROR com.servoy.j2db.util.Debug SocketAcceptor failure for socket: 8ff982[SSL_NULL_WITH_NULL_NULL: Socket[addr=/10.1.1.19,port=4665,localport=1099]]
java.net.SocketException: Connection reset
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.performInitialHandshake(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 java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.DataInputStream.readInt(Unknown Source)
at com.servoy.j2db.util.rmi.d$b.run(Unknown Source)
at com.servoy.j2db.util.as.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
WHAT is exactly freezing? all clients? the server?
what are your memory settings? server specs?
windows server? works as services?
stuff like that, we are working for more than 4 months with servoy 3.5.7 and never seen these things.
(yeah I saw it, but that was tottally us screwing things up in for example, calculations )
Could be a network router dropping connections when to long idle (the errors you showing are network-connection drops), suggestion to set the ping delay to 30 (seconds)
Shoot! Sorry, the clients hang, even if I’m running a client on the server.
It will start with a massive slow down across the board where forms take 15 to 42 seconds to load (yes, i’ve timed this). Searches on 36K record databases which took 1-2 seconds, take 5-6. Then a few clients will freeze, meaning if they are minimized they can’t maximize, or if they are using Servoy the screen will stop redrawing, either it will go grey or it will sit on the form they are currently on.
A few minutes later, after the freezes on what I can only believe are ports closing down, all the clients will stop working wherever they are at.
The average time for a query is below 2 seconds and I don’t have a lot of queries, not like thousands and thousands. There one or two that are above 1000 and those are relation queries.
2 seconds is really long, don’t you mean 2 milliseconds??
you could also check, when the clients don’t react, how many, DB connections are in use, per server.
and at that time, look at CPU or memory on the server.
Status
Server status: Online
Active connections: 0/50
Idle connections: 10/10
I have never found those settings very accurate. I will monitor networking, ram performance on the server to see if I notice anything around the time that it takes a hit.