ObjectDB Database Search

, it is an SSLSeverSocketIml . The 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 at the source code ... accept with a timeout . Build 2.8.5_07 now switches to the other method of calling accept with no timeout

operation is slow, it may indicate that this timeout may not be sufficient. support Support I am closing ... connections. Is the timeout for closing purger threads configurable, so I could try raising ... ;Is the timeout for closing purger threads configurable, so I could try raising it? No, but the 2-seconds

a few seconds after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout ... . Anyway, try using the inactivity timeout that probably may solve the problem. support Support I'm getting

process B block, or fail with an exception? If B blocks is there a timeout ? c) to configure ... process A, does process B block, or fail with an exception? If B blocks is there a timeout ? Default is immediate failure, timeout can be set -  see the documentation . c) to configure pessimistic

configurable timeout on the client size and ideally also ability to retry.  Kind regards, Natalia ... configurable timeout on the client size and ideally also ability to retry. You can try setting a timeout for queries (using a hint ).   support Support

zero inactivity timeout (e.g. 600 seconds) may solve the problem. support Support Well, I know ... issue about SO_REUSE but I honestly dont see any relation. I'll try to play with inactivity timeout ... . If it happens again after setting inactivity timeout , please report, and we will try to find the cause by adding

kind of timeout for replicated transaction. So in case when master dies in the middle of transaction ... 'phase' will gradually timeout after switching to master. This isn't the most beautiful solution

-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow-core-thread- timeout false INFO: SEC1002 ... thread-queue-capacity 2147483647 allow-core-thread- timeout false INFO: SEC1002: Security Manager

: - None "JMX server connection timeout 18" - Thread t@18 java.lang.Thread.State: TIMED_WAITING at java.lang ... $ Timeout .run(ServerCommunicatorAdmin.java:168) at java.lang.Thread.run(Thread.java:748) Locked ownable

should not rely on the standard timeout hint. Depending on the database in use and the locking

JPA Method in jakarta.persistence.Query Integer getTimeout () The query timeout . Since: JPA 3.2

that you think may be leading to this situation? Are there any timeouts that can be configured to prevent

items wont effect performance. We can also annotate them to delete with some time , some timeout . Or

I have run master and slave in 2 different remote servers when master goes off and my app get connecting to slave but it have downtime aprox. 20 sec.How can i minimize this? Manoj Manoj Kumar Maharana The timeout for switching from the master to the slave is currently not configurable

It may be a firewall restriction. If it is, specifying inactivity timeout in ObjectDB configuration may solve the problem. support Support

Is it possible to change a LockTimeout for pessimistic lock? glaz Alexandr Kurucin Currently ObjectDB throws a LockTimeoutException immediately when a pessimistic lock cannot be granted. Future versions will support timeout setting. You may fill a feature request to increase the priority of this feature.   support Support

closed when not in use anymore. In addition, you may set inactivity timeout  (disabled by

might be communicating with Database A then decide to failover to B due to a timeout . So A fails over and B is told

how to find the blocking problem ... I put a query timeout ( 300000 in value ), but it doesn't

out for a corresponding database.ojb$ file. But of course we could not wait for ever so there is a timeout wich

issue. There are many query execution timeout exceptions in the new log. Did you set a limit of 10 ... timeout exception (log #126), so hopefully we are still in the scope of query executions timeout ... that are not related to query execution timeout and if there are side effects such as slowness

UnsupportedOperationException  error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed ... . Fixed a Doctor and Replication regression (Type session exceeds timeout ). Removed  Conflicting modifiers  validation check and error message.

; query timeout could also help, at least to kill queries that no one is waiting for them anymore, e.g. after a user refresh the page. support Support we already have a query timeout . All the client

Added support of JPA UPDATE and DELETE queries ( issue #12 ). Added support of pessimistic lock timeout ( javax.persistence.lock. timeout ). Added implementation of the getParameters method. Added exception on pessimistic locking retrieval with no active transaction. Improved support of entity

We are testing client-server architecture. Our server has the following config: path = "$temp" threshold = "64mb" / inactivity- timeout = "0" / size = "0" user = "true" password = "true" / path ... = "$temp" threshold = "64mb" /                 inactivity- timeout

.concurrent.ThreadPoolExecutor$Worker) "JMX server connection timeout 74" - Thread t@74 java.lang.Thread ... .remote.internal.ServerCommunicatorAdmin$ Timeout .run(ServerCommunicatorAdmin.java:168) at java.lang.Thread

, it was created when a query that normally takes around 5 seconds was terminated by the timeout that we have set

(JpaQuery.java:686) ... Maybe caused by network inactivity timeout ? We are using the following configuration