About start

release

2.0.2

... it will be fixed within 48 hours. You should start by following the tutorial or reading the manual . For ... JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class ...

 
release

2.0.3

... it will be fixed within 48 hours. You should start by following the tutorial or reading the manual . For ... JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class ...

 
forum_thread

Activated ObjectDB still throws "Too many persistable types"

I have upgraded from 2.3.7 to 2.4.4 and now my activation won't work, throwing the dreaded com.objectdb.o.UserException: Too many persistable types (>10) - exceeds evaluation limit I have already reactivated and checked that my objectdb.conf is correctly used (by inserting random chars at the beginning of the file, which lead to an error). Yet I still get the error thrown. Nothing in my configuration changed except the version. What could possibly be the problem with that? #1 2012-10-29 14:43 I have upgraded from 2.3.7 to 2.4.4 and now my activation won't work, throwing the dreaded com. objec ...

 
release

2.0.5

... You should start by following a  tutorial or reading the manual . For ... JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class ...

 
release

2.0.4

... You should start by following a  tutorial or reading the manual . For ... JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class ...

 
forum_thread

Replication error on slave restart

I'm trying to enable replication on master server that was running with "recovery" enabled previously. I have copied database file to slave... and so on by manual. It worked fine. But if I restart slave server: ... "." mode = "write" /> Before you start replication again, copy the master database to the slave and remove any ... master (new DB file, no transactions for now) 3) Start ODB Server on slave. 4) Make changes in application (now it has ...

 
forum_thread

Deadlock in objectdb code

Running multi-threaded access to an embedded database using JDO, I'm getting a deadlock in objectdb code.  Thread dump attached. ... a convenient way to introduce classes to objectdb at the start of a run, so they aren't first encountered later?  Also, is ... a convenient way to introduce classes to objectdb at the start of a run, so they aren't first encountered later? You can ...

 
forum_thread

Working with a cleared cache

I'm working on trying to improve the performance of our database processing class and I'm attempting to keep the L1 cache within the PersistenceManager cleared in an effort to reduce its memory footprint. The code snippet below is part of a Callable task that is run repeatedly with a given list of commands. When I run the code as written I start getting the stack traces that are listed.  However, if I comment out the calls to makeTransactionalAll() and evictAll() everything works.... a given list of commands. When I run the code as written I start getting the stack traces that are listed.  However, if I comment out ...   try { // Start the transaction m_persistenceManager. currentTransaction ...

 
api-jpa

substring(x, from, len)

Create an expression for substring extraction.(Method of javax.persistence.criteria.CriteriaBuilder)

 
forum_thread

Listing large number of complicated objects with paging.

Hi, For last few hours I was working on a problem with bad performance and memory problems with such a simple query: select prod from Product prod order by prod.id ASC Right now I have 55541 'Product' (attached to this post) entities in database and I'm trying to speed listing them with paging. The problem is, that running code that looks like this: ... ; prodList = icQuery. setFirstResult ( start ) . setMaxResults ( count ) . getResultList ... DEBUG pl.hplxtool.dao.impl.ProductDAOImpl - Start: 250, count: 50 2011-11-15 19:31:03.219 [http-bio-8080-exec-3] DEBUG ...