Internal Website Search

.jar has not been created for this purpose. This specific reported exception indicates a failure

may still see objects as locked. Naturally lock failures are more common when using more threads. support

Walezy There are several possible causes of failure mentioned in your post: The {} syntax

during development and testing can help in identifying failures . If the Doctor reports broken references

.afterCompletion - returned failure for SynchronizationImple 13:52:32,388 ERROR [org.jboss.ejb3.invocation

I might also be seeing a failure of my OEM license when using ObjectDB 2.7.2_03. [ObjectDB 2.7.2_03] javax.jdo.JDODataStoreException Too many persistable types (10) - exceeds evaluation limit (error 1011) at com.objectdb/com.objectdb.jdo.JdoQuery.compile(JdoQuery.java:734) I

.  The attachment upload reported a failure again.  This time I captured a screenshot. 

If I create a replicated database cluster as per http://www.objectdb.com/java/jpa/tool/replication what is the behaviour of the master database after a failure ? For example, say I have MasterDB and SlaveDB in the cluster. If MasterDB goes offline the application will automatically switch

the closed connection on JVM shutdown, does that include JVM failure (out of permgen space) and forced

will be completed. Even if there is a failure , restarting the slave and the connection to the master

by a commit failure ." Quite different behavior from what I expected and would prefer. 

is immediate failure , timeout can be set -  see the documentation . c) to configure pessimistic

The exception is thrown by the Java XML library due to a failure to open the XML file for validation

. avoid empty catch which results in quite failure ). If ObjectDB throws an exception

failures . Regards, Natalia. natmaclin Natalia Levine I've also just noticed that the error is different

back with failure message {"JBAS014671: Failed services" = {"jboss.deployment.unit.\"Guestbook.war

a special protocol (rsrc:) - the result could be a failure to handle these paths. Setting 

Mike Keith believe the JDO is out of date. Then what role of JDO in ObjectDB? Will our codes with JDO be out of date? Due in part to some of the failures of the EJB persistence model, and some frustration at not having a satisfactory standardized persistence API, another persistence specification

2 separate mechanisms for recovery from failure : Recording (transaction log). Recovery (double

: 14, Failures : 1, Errors: 0, Skipped: 0, Time elapsed: 1.35 sec

for this failure is still unclear. But enhancement is certainly recommended in production as

enough about the situation to know if this behaviour is expected, but the failure does seem like a bug

- 2) Deployment of "Guestbook_Jee.war" was rolled back with failure message {"Services with missing

), etc., since this may be the first report of a failure in this specific code. support Support

annotations of some class leads to a failure due to a missing class in the classpath. Maybe future

the same (deployment failure ). The version of JBoss was 7.0.x at that time and lots of declaration

:212) ... 33 more   mbana mbana The exception indicates a failure to find a persistence unit

the changes,persist and commit? cpanon CP By default, objects after transaction failure (regardless

Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure . Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a  NullPointerExeption on new index building

Not sure if this is an objectdb issue or not but I thought I'd raise it just in case. We had a server failure which caused an unexpected reboot. As a result, the application services which use objectdb were not shutdown properly which in turn meant we had several odb$ files left behind. I

on the system for Jstack, I hit a failure to a permissions error on the /tmp directory I just

from failure should protect data and indexes, so we will have to investigate this further. As

component that causes this query execution failure ? Does it have navigation through null

? Could it be because of the superclass, as I guessed? Or a failure of run-time enhancement? RDBMS-based JDO

BTC EmbeddedSystems It seems like a  failure in automatic tracking of changes in enhanced classes

trace indicates a failure to cascade persist operation from unknown reason during that flush. Any

it further we will need your help. Are you sure that the only difference between a successful run and a failure run

the cache. thumbripper Richard Szurgot Your test demonstrates a failure of ObjectDB in evaluating

a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding

are possible (although very rare). It may also cause a failure in updating indexes in some very specific

{   *****POINT OF FAILURE ***** */       reportDownloadObjects = query

#2 reflects a locked database file (due to a failure during close) and not a corrupted database

the failure , it may not cover some other specific case. Investigating the corrupted database

in the test if you can't deduce the exact failure from this. kaosko Kalle Korhonen

which was causing the failure because of a filter.. sorry!! Alex quasado Alexander Adam No problem

the primary key so I would expect to see wider app failures if it was null. 2012-02-24 18:39:55,719

Improved recovery from failure when recovery is enabled with no sync  ( issue #2293 ). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading ( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed