14 | OptimisticLockException with an exception? If B blocks is there a timeout? c) to configure pessimistic locking, all I do is set ... 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 locking, all I |
14 | Log is almost empty (log level 'trace'). due to inactivity) by the operating system, firewall, etc. In that case setting a non zero inactivity timeout ... dont see any relation. I'll try to play with inactivity timeout and let you know results. Yuri ... timeout, please report, and we will try to find the cause by adding logging information |
11 | Entity is not related to ObjectDB, but i get exception from ObjectDB> <properties> <property name="javax.persistence.query.timeout" value="20000"/> <property name="javax.persistence.lock.timeout" value="2000"/> <property name="jboss.as |
11 | 500Mb ObjectDb database opening issue500Mb ObjectDb database opening issue |
11 | EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable" threshold="64mb" /> <network inactivity-timeout="5" /> <url-history ... inactivity-timeout="5" /> <url-history size="50" user="true" password="true |
11 | Improvement in replication 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 |
11 | How to do multithreading with embedded ObjectDB. Use ObjectDB / JPA locking, by setting a pessimistic locking timeout, e.g. by: Map<String, Integer> properties = Collections.singletonMap("javax.persistence.lock.timeout", 1000 |
2 | each 1-2 days objects on some objectdb level lock/block each other" threshold="256mb" /> <network inactivity-timeout="0" /> <url-history size="50" user ... . support Support Maybe setting query timeout could also help, at least to kill queries ... we already have a query timeout. All the client/server interaction is running through a webSocket connection |
2 | ObjectDB 2.3.1 UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug (issue #520). Fixed ... a Doctor and Replication regression (Type session exceeds timeout). Removed Conflicting modifiers validation check and error message. |
2 | ObjectDB 2.2.4Added 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 objects |
