Clients Locking Up

Classic Servoy
1

Hi Mighty Servoy Crew.

We have a client who is using the same solution that our other clients use.

But for some reason, their clients have been locking up after 20 minutes or so.

So, knowing that this isn’t normal, I’ve been using my detective powers to try to figure out what might be going on.

So, I first went to the servoy-admin/log and saw this error many times:

com.servoy.j2db.persistence.RepositoryException: paygo_db: Thread tried to acquire lock which it already owned, transaction id=37, thread=RMI TCP Connection(420)-69.27.5.26 
    	at com.servoy.j2db.persistence.Server.a(Unknown Source) 
    	at com.servoy.j2db.persistence.Server.getTransactionForId(Unknown Source) 
    	at com.servoy.j2db.dataprocessing.TransactionManager.do(Unknown Source) 
    	at com.servoy.j2db.dataprocessing.SQLEngine.a(Unknown Source) 
    	at com.servoy.j2db.dataprocessing.SQLEngine.performQuery(Unknown Source) 
    	at com.servoy.j2db.dataprocessing.SQLEngine.performQuery(Unknown Source) 
    	at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source) 
    	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
    	at java.lang.reflect.Method.invoke(Unknown Source) 
    	at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) 
    	at sun.rmi.transport.Transport$1.run(Unknown Source) 
    	at java.security.AccessController.doPrivileged(Native Method) 
    	at sun.rmi.transport.Transport.serviceCall(Unknown Source) 
    	at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) 
    	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) 
    	at java.lang.Thread.run(Unknown Source)

And also, this one appeared:

avax.net.ssl.SSLHandshakeException: no cipher suites in common 
    	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.ServerHandshaker.chooseCipherSuite(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientHello(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) 
    	at com.sun.net.ssl.internal.ssl.Handshaker.process_record(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)

Each of these errors appeared over and over in the log… making me assume that as the server does this… it suspends the client… giving them the feeling of frozenness.

Anyone have any ideas here. We’re pretty new to Servoy and most deployments have been dandy… but this one is a tough one.

Chico

2

that second SSL error is just weird and really basic java/os stuff that could go wrong
You could try to update, dont know what os and java version they are using, the java version to the latest 1.6

that second is also hard, somehow the transaction is taken twice for the same call to the server (to do a query)
does this only happen when that specific client is connected? or also for other clients?