Internal Website Search

We had a database failure causing a production outage. Both master and slave databases have failed ... -only mode so this is also unexpected. Is it possible that actually the failure started on the master ... too much resources, maybe because of repeating attempts?) As you know, master failure currently requires

due to various reasons: Hardware failure (e.g. a physical disk failure ). Software failure (e.g. a bug ... . Network or I/O failure when copying, moving or transferring a database file. Transferring a database file ... without its recovery file or recording directory. Power failure when the database is being updated

without support instantly available for many years.  How stable is ObjectDB when it comes to power failures ... failures .  Is ObjectDB suitably robust that it won't fail in such situations?    ... on power failure :  Recovery File and  Recording . If you try a 'kick the plug

more FAILURE : Build failed with an exception. dmoshal David Moshal If you switched to Java 9 then you need

Optimistic locking failure : I am using a Semaphore to force this execution of concurrents transactions T1 and T2 that cause parallel updates to A/B but it does not throw an OptimisticLockException and roll back. T1 T2 ---------------------------------------------------------- READ(A) version=1

failure to enforce NOT NULL for java.lang.String

Merge failure with composite primary key

JDOHelper.isDetached failure ?

Failure after ObjectDB 2.4.5_07 upgrade from 2.4.4_06

transaction is represented by: Database update failures that require transaction rollback are represented by: The RollbackException exception usually wraps the real failure cause as a nested exception  ... entity object, the nested exception is: Other common causes for RollbackException are lock failures

can be used to fix the database. Recovery from failure is automatically applied by ObjectDB ... (which modify the database) have to be recorded. For debugging of query failure

is useful for two different purposes: It enables recovery from a database failure by replaying the recorded operations. It enables reproducing problems during debugging by repeating a failure . Backup

, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses

of rollback or by a commit failure . Explicit Merge Detached objects can be attached to any

cure such failure in a reasonable period of time after becoming aware of such noncompliance

to the database prior to the failure ) and a RollbackException is thrown.

Recovery from failure by using a  recovery file and double writing. Additional recovery layer

locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level rollback Parameters: entityClass - entity class ... but cannot be locked: the PessimisticLockException will be thrown if the database locking failure causes

only mode. This requires some operations by your application: identifying a failure , moving ... solution is to create a marker file (even empty) on the master server file system and on failure to delete ... will work at all. Here is the reason: in some cases failures are not consistent. Let's say the NIC

and there is a high likelihood of deadlock or update failure among concurrent updating transactions ... cannot be obtained, and the database locking failure results in transaction-level rollback, the provider ... has been marked for rollback. When the lock cannot be obtained, and the database locking failure results in

" to see if there is some class loading failure for SingleFieldIdentity.  No failures , except for class "String ... we see the ObjectDB failure , as you describe, because Java 9 module blocked a class loading via reflection

if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level rollback If a vendor-specific

will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level rollback If a vendor

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes

: the PessimisticLockException will be thrown if the database locking failure causes transaction-level rollback the LockTimeoutException will be thrown if the database locking failure causes only statement-level rollback

showing a true failure ? import javax.jdo.JDOHelper; import javax.jdo.PersistenceManager; import javax ... the cache, like it was told to do).  If I manually set ignoreCache=false to correct the failure

for more than one request, failure to read a full request by the server can cause next requests to fail ... , until you can identify the specific part of the application that is relevant to the failure . support

If previously stored objects are missing it could be either due to a failure to persist them, failure

project. Success stories (as you mentioned) are well known. Failure stories may be more common and much less known. One specific failure story that we know about is related to a known open source object

back modifications that have already been propagated to the database prior to the failure ... . power failure ), and before the changes are able to be completely written to the database

JPA Method in javax.persistence.criteria.Expression Expression as (   Class  type ) Perform a typecast upon the expression, returning a new expression object. This method does not cause type conversion: the runtime type is not changed. Warning: may result in a runtime failure

conversion: the runtime type is not changed. Warning: may result in a runtime failure . Parameters

type is not changed. Warning: may result in a runtime failure . Parameters: type - intended type

is not changed. Warning: may result in a runtime failure . Parameters: type - intended type

is not changed. Warning: may result in a runtime failure . Parameters: type - intended type

When the Doctor completes please post its output. Exploring the cause of the recovery failure ... . Actually this is the first report of such a failure after recovery. Probably you do not ... of the recovery from failure . However, there is also a possibility that some sort of optimisation

of possible causes: Hardware failure (e.g. a physical disk failure ). Software failure (e.g. a bug ... . Network or I/O failure when copying, moving or transferring a database file. Transferring a database ... without its recovery file or recording directory. Power failure when the database is being updated

which blew out the logs: Attempt to commit a transaction after failure in writing to database file 'F ... to commit a transaction after failure in writing to database file 'F:\calculationservice\objectdb\dbs ... .objectdb.o.UserException: Attempt to commit a transaction after failure in writing to database file 'F

the Doctor. support Support Can data in ObjectDB be lost in case of power loss or arbitrary system failure ... in case of power loss or arbitrary system failure ? With ext4 and journal this is not possible. In ... . If the database is not corrupted then the exception is probably not related to the power failure . We need

.RollbackException Failed to commit transaction: Attempt to commit a transaction after failure in writing ... to commit a transaction after failure in writing to database file 'F:\calculationservice\objectdb\dbs ... : com.objectdb.o.UserException: Attempt to commit a transaction after failure in writing to database

on unexpected network failure . Improved temporary file management including avoiding permission ... an InternalException in query execution ( issue #739 ). Fixed a master server failure ... queries. Fixed recovery from failure when the recovery file is empty ( issue #695 ). Removed

, which could possibly happen due to an unknown server failure . The database file will not help here, but just verify ... ;Approximate failure times were 8/29 @ 11:54 AM, 8/30 @ 7:41 PM, 9/1 @ 12:15 PM (all times PDT

to see this issue, as well as the mismatch client-server protocol prefix failure , and some other problems ... protocol prefix failure again. FastModel Ben Schreiber Since your system ran with ObjectDB for a long

to these failures , as there are no timestamps that I can use for cross-referencing. Can you please determine root ... at all. The exception doesn't indicate a failed transaction but a failure of the server to cleanup

after failure in writing to database file 'C:\Users\Home\workspace\Object.Test\test\persistTest.odb ... : Attempt to commit a transaction after failure in writing to database file 'C:\Users\Home\workspace

is enabled and there is a failure in writing to the database file, ObjectDB repairs the database file ... . But the recovery file (ended with $) must be available when the database is opened after a failure . support Support

the code.  I have run into issues during testing such as failures to deserialize ... during testing such as failures to deserialize because of incompatible stream serialVersionUIDs

.JDOOptimisticVerificationException This class represents optimistic verification failures . The nested exception