18 | ObjectDB is opening too many sockets, it is an SSLSeverSocketIml. The accept method has a timeout of one second and after that timeout another accept is called ... accept with a timeout of 2 seconds, in a loop, in order to check for server stop requests. Looking ... -a-serversocket-accept-method As discussed, ObjectDB used a loop of calling accept with a timeout |
18 | ODB-WeakRefPurger threads not closing at all seconds for that thread on close. If your close operation is slow, it may indicate that this timeout ... PersistenceManager instances to track DB connections. Is the timeout for closing purger threads configurable ... . > Is the timeout for closing purger threads configurable, so I could try raising it? No, but the 2-seconds |
16 | Server connection management server in a few seconds after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout in seconds and it affects both the client and the server side: <general> ... <network inactivity-timeout="3600" /> ... </general> Connection Pool (Client |
16 | Occasionally slow requests in load testing-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="$objectdb/log ... is to have a per-client configurable timeout on the client size and ideally also ability to retry. Kind ... is to have a per-client configurable timeout on the client size and ideally also ability to retry. You can try |
4 | setHint(hintName, value) on the standard timeout hint. Depending on the database in use and the locking mechanisms used by |
4 | lock(entity, lockMode, properties) ignored. Portable applications should not rely on the standard timeout hint. Depending on the database |
4 | refresh(entity, lockMode, properties). Portable applications should not rely on the standard timeout hint. Depending on the database in use |
4 | find(entityClass, primaryKey, lockMode, properties). Portable applications should not rely on the standard timeout hint. Depending on the database in use |
4 | setHint(hintName, value) timeout hint. Depending on the database in use and the locking mechanisms used by the provider, this hint |
0 | find(entityClass, primaryKey, lockMode, properties) applications should not rely on the standard timeout hint. Depending on the database in use |
