ObjectDB Database Search

101-120 of 120 results


	Embedded & Activation & Scalation folder, however I've got a few questions I couldn't find answers for: How will locking take place
	Multithreading Test and Deadlock MBs). support Support Thanks. It solved the dead lock . edy_at_ssn Edy Oey
	Bulk Delete and Update - best practice? based databases (in server mode the database is locked so drop can't be used). The only method I've
	Entity is not related to ObjectDB, but i get exception from ObjectDB ?   Could you please clarify how we could avoid it? This has really locked our work for a couple of days
	Updating Entities ._OptimisticLockException: Optimistic lock failed for object application.model.Paygrade#184 (object
	FileNotFoundException I'm sometimes getting this exception. Is there a simple answer to why it's occurring? (It could take some time to produce code that results in this exception reliably). Caused by: java.io.FileNotFoundException: /tmp/objectdb/tmp/objectdb_1252962966569709153/ lock .lck (No such file or
	Getting exception while executing the Query I have facing a problem when i am executing the query first time, Please find the stack trace below java.lang.InterruptedException at java.util.concurrent. locks .AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1301) at java.util.concurrent.Semaphore.acquire
	Should I use ObjectDB and JDO? because JPA was more popular and thus receiving more support, and JPA object locking was more capable
	Unable to execute update query :745) Xmx is 4GB. This is how the tmp directory looks like after the error occoured: 0 lock .lck 4,0K
	NPE at com.objectdb.jpa.JpaQuery.getResultList O'Hare It seems as a separate issue. Maybe related to pessimistic locking . Can you provide a test
	ObjectDB 2.3.2 instead of Long ) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.
	ObjectDB 2.3.1 UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed
	Best practise loading big data that is somehow locked . Closing the entitiy manager should free the memory - but freeing no longer objects
	Remove an entity which attributes were changed lock exception of the removed entity. If this operations on the entity are executed in
	ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.
	Removed entities can be found by query in the same transaction . It solves another issue (unexpected optimistic lock exception) but you may want to check if it also solves this issue. support Support
	ObjectDB 2.1.0 Added Online Backup utility ( issue #16 ). Added Master-Slave Replication / Clustering (issue #17 ). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects (included in the download). Added support of disabling optimistic locking
	WeakRef Purge ObjectDb threads not stopping with Tomcat (in application container) on (a java.lang.ref.ReferenceQueue$ Lock ) at java.lang
	EOFException engine (not using one server process), thus bypassing ObjectDB internal file lock protection
	javax.jdo.JDONullIdentityException: The identity must not be null. #2 reflects a locked database file (due to a failure during close) and not a corrupted database