Illya Kysil

hi @tglman No positive changes with the latest OrientDB 3.2.40, unfortunately. It looks like the problem got even worse during the schema creation. I am updating the [reproducer](https://github.com/ikysil/orientdb-issue10453-reproducer) project so...

hi @tglman The [reproducer](https://github.com/ikysil/orientdb-issue10453-reproducer) project has been updated. The testing procedure is much simpler now - make sure to check the README. OrientDB releases 3.2.39 and 3.2.40 are affected, while...

We did another attempt to upgrade from 3.2.38 to 3.2.40 in our DEV environment today, application is using client 3.2.40. There are 3 master nodes in DB cluster and they...

> trace the client and add the log here, you can do this running the test like `./mvnw clean test -Dnetwork.binary.debug=true | tee network_traces` and than attach somewhere the network_traces...

After rollback to OrientDB server 3.2.38 we still observe `Cannot find a valid session for subscribe for event` messages on the client side but we DON'T observe `java.net.SocketTimeoutException: Read timed...

Hi, The [reproducer](https://github.com/ikysil/orientdb-issue10453-reproducer) project has been updated again. The tests fail with newer versions of OrientDB server with the following exceptions: ``` com.orientechnologies.common.io.OIOException: Error on connecting to localhost:2424 at com.orientechnologies.orient.client.remote.ORemoteConnectionPool.createNetworkConnection(ORemoteConnectionPool.java:48)...

Hi @tglman I've checked our main application with the latest release 3.2.41, using cluster with 2 MASTER nodes and 1 REPLICA. Initial state of the cluster with new empty database:...

More stats for the previous report:  There are only two connections open from the app to the OrientDB server:  There are 19 sockets open by the OrientDB server...

> ...this logic was changed to use monotonic time in 3.2.38....... There are changes between 3.2.38 and 3.2.39 where usages of `System.currentTimeMillis()` were replaced by `System.nanoTime()` (through `OToken.timeMillis()`). It looks...

Hi @tglman The scenario has been confirmed - the client app is re-creating a connection (session) for each command. Both server and client app run OrientDB 3.2.41 release. Check the...