path="$temp/ObjectDB" threshold="8mb" />
timeout="0" />
timeout on the client size and ideally also ability ... configurable timeout on the client size and ideally also ability to retry. You can try setting a timeout for queries (using a hint). natmaclin

after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout in seconds ... -timeout="3600" />
...
Connection Pool (Client Side) You should be able to set ... . Anyway, try using the inactivity timeout that probably may solve the problem. I'm getting the same

the operating system, firewall, etc. In that case setting a non zero inactivity timeout (e.g. 600 seconds ... to play with inactivity timeout and let you know results. Yuri The server can quit silently when it gets ... . If it happens again after setting inactivity timeout, please report, and we will try to find the cause by

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