ObjectDB Database Search

for every topic and use the issue tracking for clear ObjectDB bugs. Regarding logging - the ordinary

: Why objectdb cause so many memory that it fails with "-Xmx1432m", even if em. clear () at every 0xFFF

.getTransaction().begin(); em.persist(data); em.getTransaction().commit(); em. clear (); TypedQuery q = em

Hello,   My apologies if the answer is already on the website, but I’m struggling to find a definitive answer.  The 10 entity class restriction is very clear , but can each of these classes use unrestricted numbers of embeddable classes?  Do embeddable classes count as

back all         em. clear (); ///

; originalOrganisation.getElectronicAddresses(). clear ();          

, and clearing the EntityManager at transaction end. support Support Hi Great support .. thanks for the timely

there is no field value on Column annotation but i need solution like that on pure JPA if possible. Fastest clear

; So to be absolutely clear ... the enhancement takes place around the assignment of a persistent field, not

." Grateful for feedback (although the problem is somewhat academic as a solution is clear ), Webel

help. Please clear my doubt I know JPA is just a Specification and ORM Frameworks like Hibernate

J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting -Dobjectdb.temp.no-resize- clear =true The only other change is that we no longer create recovery or replay files as we were not using these. i have attached our full server strack trace

. Is there a similar option für ObjectDB? If I were unable to make myself clear , here's what I want in

- from the ObjectDB manual - by: "The following operations clear the entire persistence context

Source) mimac Milan Fabian OK. Apparently the problem is clear now, and we are working on a quick fix

We should add this ability in future ObjectDB versions, thank you for making this point clear

;are clear selling points. (JPA and JDO APIs versus an elegant proprietary API is a negative

you for this report and for the clear test case. Please try build 2.5.4_03, which should fix

is clear . This solution could work with multiple applications only if all the applications always select

Hi, We have a memory leak in our application which seems to be related with ObjectDB. Basically, we use single instance of EntityManager, which is opened on aplication initialization and closed when the user logs out, as well as EntityManagerFactory. We use em. clear () after every commit

to overcome the problem by using flush(), clear () and refresh()  hgzwicker Hans-Georg Zwicker Good

to pass a non entity object to merge should throw an exception with a clear error message

already made, but they seem to be ignored. So, my (and my company's) wish is to see a clear roadmap of ObjectDB

completely clear . A blocked thread is not necessarily a problem. There is an essential synchronized

;    em. clear ();         TypedQuery q = em

",     personID)   .executeUpdate(); em2   .flush(); em2   . clear (); tr

update page http://www.objectdb.com/java/jpa/setting/schema it is not clear how to handle this case

described in post #3 clear enough. The other message is because we have referenced the ObjectDB

Hi, I am running a java application that records data from 100 feeds into 100 different database - this is done is one thread. It works fine several hours - and suddenly i got an out of memory issue (I checked there is no leak in java - I cleared the entity manager every 10 new entity) - I run

subclasses of NamedEntity the field will be initialized as null . support Support Perfect. Thanks for clearing up. btc_es BTC EmbeddedSystems

Hello, As stated above, I would like to know if it is possible to commit only specific elements, or at least update a single table, disregarding the other entities loaded in the persistency context? I have a complex hierarchy of intertwined objects. Currently I am clearing my persistency context

Key is separate so i can use indexes, thank you for the documentation on this topic, concise and clear as usual. Thank you support lo Hoel

is clear I guess. Must add that I am using the Glassfish server 4. I didn't somehow configure JAX-RS

regards Arne   PS.: maybe I should make clear , that Testclass uses its own equal and hash methods

A shutdown hook is registered upon ObjectDB initialisation. The hook is loaded from the web application's class loader. When the application is stopped (not the server, just the application) the hook is not cleared . This leads to web-application class-loader leak, that results in huge resource

(..) call the object is ok. Inside the @PrePersist method all fields are cleared .  mosi0815 Ralph Moser

- the map is loaded and its contents are printed. On the second run (without deleting or clearing

(JpaQuery.java:722) ... 15 more This occured when the app tried to clear data for a particular id

Remove the entity object, EntityManager is flushed & cleared , Transaction is not committed Count

it but we're not clear what is happening yet 2) No replication is in use - the database in question

to clear the collection first, commit that and then remove the Contact? thanks! quasado Alexander Adam

of that exception? It is clear that you get a NoResultException that you do not expect. A test case

it - it could help. In this case the test can be complex since the bad result is very clear . Your last test

this specific case is in the query or in ObjectDB. It is clear , however, that $3 should be replaced

.class); bensteele Ben Steele Maybe it was a cache problem and restarting the database cleared the cache

this problem. Regarding the sequence names, the JDO specification is not completely clear . Do you expect

only stated, that the transaction has been marked for rollback. Why it has been marked was not clear

, and on complete clean and build in NetBeans, and also after complete NetBeans cache clear

for each, and possibly also  clear  after commit ) Using classes that are not enhanced. In

of embedded objects to collections. Fixed database page objects reuse to release to be cleared