Home » Search

About PESSIMISTIC_WRITE

81-90 of 200Refresh
JDO Doc
1

writeExternal(out)

Method javax.jdo.identity.LongIdentity void writeExternal(   ObjectOutput out ) Write this object. Write the superclass first. Parameters: out - the output Since: JDO 1.0
JDO Doc
1

writeExternal(out)

Method javax.jdo.identity.ObjectIdentity void writeExternal(   ObjectOutput out ) Write this object. Write the superclass first. Parameters: out - the output Since: JDO 1.0
JDO Doc
1

writeExternal(out)

Method javax.jdo.identity.ShortIdentity void writeExternal(   ObjectOutput out ) Write this object. Write the superclass first. Parameters: out - the output Since: JDO 1.0
JDO Doc
1

writeExternal(out)

Method javax.jdo.identity.StringIdentity void writeExternal(   ObjectOutput out ) Write this object. Write the superclass first. Parameters: out - the output Since: JDO 1.0
Forum
1

Pessimestic Locking doesn't release when application unexpectedly terminates.

) is to use pessimistic locking with expiration time. For example, if you know that transactions ... is broken. Hi Since I want to use Pessimistic Lock as a way of enforcing a cluster wide singleton of services, a pessimistic lock will potentially last forever or until the particular service goes
Forum
1

Optimistic locking failure

| B = A + B + 20 | WRITE(B) version=2 value=20 A = A + B + 10 | WRITE(A) version=2 value=10 ... . Please explain the test output: Sequential=true Lock=WRITE Thread[Thread-2,5,main] READ  A1 version=1
Forum
1

Error 363 - Failed to read value of inverse relationship

beforeCompletion() callback: [ObjectDB 2.2.8_01] javax.persistence.PersistenceException Failed to write ... .objectdb.o.UserException: Failed to write the value of field property edu.um.fcsit.jpa.entity.Guest ... : [ObjectDB 2.4.1_07] javax.persistence.PersistenceException Failed to write the value of field
Forum
1

OptimisticLockException

. Also have the Explorer open Questions: a) what is it about? b) is there a setting for pessimistic mode? In my app, I ... a pessimistically locked entity (global tracking id generator, specific to internal requirement) - and got ... Optimistic lock error on pessimistically tracked entity.   Modified conf file, and got the test case
Forum
1

Master database switching to read-only mode, possibly caused by slave failure

- MASTER instance stopped responding to write requests. All requests sent to the database during 3 ... and there was nothing in the server DB logs. All write requests sent to master after this time have failed ... are executed and WRITE requests are rejected. Maybe even the high GC on the slave is the result
Forum
1

best practice for DB recovery

and add them to my persistence unit but being able to read and not write is a condition that can't last ... have two(or more) entity managers in my DAO layer and write all changes to both instances(may have IDs synchronization issues), if one of the instances is not available, I'll keep writing to the instance