Internal Website Search
21-30 of 80 resultsRefreshObjectDB is opening too many sockets class="code">accept method has a timeout of one second and after that timeout another accept ... ;with a timeout of 2 seconds, in a loop, in order to check for server stop requests. Looking ... with a timeout. Build 2.8.5_07 now switches to the other method of calling accept with no timeout | |
ODB-WeakRefPurger threads not closing at all on close. If your close operation is slow, it may indicate that this timeout may not be sufficient. Is the timeout for closing ... ="/java/jpa/persistence/overview">this manual page. > Is the timeout for closing | |
Server connection management after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout in seconds ... > ... <network inactivity-timeout="3600" /> | |
Occasionally slow requests in load testing; <network inactivity-timeout="0" /> <url-history size="50" user="true" password="true ... order to limit the impact of this issue is to have a per-client configurable timeout on the client ... that would be really helpful in order to limit the impact of this issue is to have a per-client configurable timeout | |
setHint(hintName, value) a provider must be silently ignored. Portable applications should not rely on the standard timeout | |
lock(entity, lockMode, properties) on the standard timeout hint. Depending on the database in use and the locking mechanisms used by | |
refresh(entity, lockMode, properties) ignored. Portable applications should not rely on the standard timeout hint. Depending | |
find(entityClass, primaryKey, lockMode, properties) should not rely on the standard timeout hint. Depending on the database in use and the locking | |
setHint(hintName, value) ignored. Portable applications should not rely on the standard timeout hint. Depending | |
find(entityClass, primaryKey, lockMode, properties) on the standard timeout hint. Depending on the database in use and the locking mechanisms used by the provider |