ObjectDB Database Search

= subject.getPrincipals(); if (principals != null) { principals. clear (); } return false ... logout() throws LoginException { final Set principals = subject.getPrincipals(); principals. clear

to stop master, clear all recording files, switch to all mode: Then I stopped also the slave Removed ... again after clearing transaction files which would be unpleasant. However, for replication you only need the last

MyApplication If the classes are not enhanced, at least call the clear method of EntityManager ... , so I'm not sure I can call clear on entity manager, anyway thanks for your help. 4410 Arsenii So just

;  em.getTransaction().commit();         em. clear ();    ... Keskes Thanks for the clear test case that demonstrates the issue. Please try version 2.5.6

to clear field property com.contextspace.AddressTest$AbstractContactDetail.type using reflection (error ... .RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: com.objectdb.o.UserException: Failed to clear

layer). If after reading the other thread you have a clear picture of how you think ObjectDB ... , currently this is not automatic. Fill a detailed feature request if you have a clear picture of how you think ObjectDB should handle this. support Support

predefined and might be added dynamically), if I didnt explain the problem clear enough please let ... of 'singleton persistent objects' is clear . You wrote: "This is what i can achieve if i have ability

. Specifically: is it advised to use a new EntityManager with every transaction, or to use one, and clear ... a detached entity object (e.g. after clear ). It doesn't seem to be related to the IDE that you use. support

statistics. You can see that suddenly on starting some index is cleared (doctor should correctly create ... demonstrate the ~20 seconds in a consistent way? It is just not clear from post #1. support Support

; at com.objectdb.jpa.EMImpl. clear (EMImpl.java:414) ~[EMImpl.class:na]       ... ;  at com.objectdb.jpa.EMImpl. clear (EMImpl.java:411) ~[EMImpl.class:na]     

.getTransaction().commit();         em. clear ();     ... ;   em.getTransaction().commit();         em. clear

; /**      * Clear the content of the originalString.      *      * The OriginalValue must be cleared if the value has been changed.  

.objectdb.o.PGC:w: line number 232) is less clear . It points to a synchronized statement. Maybe ... .no-resize- clear , to true - to enforce a quick file resizing.     support Support    

of a specific parent? Having a parent with 500K children, when I clear the list by parent.getChildren(). clear (), it loads all children then empties the list and save the change. Is it possible

more @OneToOne gives: [ObjectDB 2.4.1_01] javax.persistence.PersistenceException Failed to clear field ... .main(RemoteTestRunner.java:197) Caused by: com.objectdb.o.UserException: Failed to clear field

:     System.setProperty("objectdb.temp.no-resize- clear ", "true"); Alternatively ... is cleared with zeros. With this settings, the new file space may contain garbage (such as data from

Hi! I'm facing a really strange behavior, which I can't yet reproduce, but it happened 3-4 times already. ObjectDB seems to clear some fields that are @ElementCollection Set of my objects ... is unclear. What do you mean by clearing some fields? Please clarify. support Support The field

clear   Edit: Sorry. Solved. The code was working, the problem was that i'm savin an empty string "" (not null) elnll002 Facundo Curti

;          lstSup. clear ();      

= tn2.getTa();   System.out.println(Arrays.toString(la));   em. clear ();     tNode

are removed/deleted from the databases - it is the application responsibility to clear any references

' again of cleared up the issue. As I assign no ID's in my GUI - it seems that there could be a small bug? I'm

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

. support Support Thanks for your prompt and clear answer. I am greatly relieved to now understand

pm = pmf.getPersistenceManager(); // Clear out existing objects pm.currentTransaction().begin

;  em. clear ();     trans.begin();    }   }   trans.commit

Hi, I've never used an OODB, I'm looking for a starting point but a recurrent concern is the Data Portability one. More clear : what options / strategies do I have to export / move my data to another  tool, if there is a need to? One key point of Ojectdb (as far as I had read) is Code

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

back all         em. clear (); ///

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

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

dump. There is a clear indication that the configuration was updated successfully and a cache size

.getPersistenceManager();         // Clear out existing objects

Bimal kumar dalei Unfortunately the problem is not clear . If you print objects of a class

documentation. Below is an example that has #1 and #2 together. Additionally it's not clear how I find

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

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

, it was not completely clear to me if this setting controlled how many internal threads ObjectDB uses

.getTransaction().commit();         em. clear ();       ... ;      em. clear ();         em.close();   

. felixobjectdb Richard Szurgot Sorry! - I've double checked the test and it is bad. I'm not clearing ... I can tell is that the problem occurs after I restart the server & test without clearing

 generic classes is also not supported. ObjectDB should probably produce a clear error message in ... :  ObjectDB should probably produce a clear error message in that case. Yes it should, to help

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

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

-Georg Zwicker just to make clear : all queries are slow, not only the above example hgzwicker Hans

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

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

().commit() em. clear () System.gc(); em.getTransaction().begin(); // here we had a break point and did

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

collection happening to clear the memory from the CST/BYR objects.  I'm not sure

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