 2 | Version 2.2.4 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 |
2 | . Improved UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug (issue #520 ... RCP. Fixed a Doctor and Replication regression (Type session exceeds timeout). Removed Conflicting modifiers validation check and error message. |
2 | 500Mb ObjectDb database opening issue |
2 | .java:686) ... Maybe caused by network inactivity timeout? We are using the following configuration timeout="3600" /> This exception stack trace may indicate a mismatch |
2 | |
2 | " threshold="64mb" />
timeout="5" />
timeout="5" />
|
2 | -size 32 thread-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow-core-thread-timeout false ... -core-thread-timeout false
INFO: SEC1002: Security Manager is OFF.
INFO: SEC1010: Entering Security |
2 | / JPA locking, by setting a pessimistic locking timeout, e.g. by:
Map properties =
Collections.singletonMap("javax.persistence.lock.timeout", 1000 |
2 | . On slave server (and only on them) there can be some kind of timeout for replicated transaction ... transaction on new master. Old transactions from slave 'phase' will gradually timeout after switching |
2 | >
timeout="0" />
timeout="0" />
|