[OJB-141] Objects are not evicted from Cache on abort() after flush() - ObjectEnvelopes reuse mechanism fails

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.4, 1.0.5
• Fix Version/s: 1.0.4, 1.0.5
• Component/s: ODMG-API
• Environment: -
• Assignee: Armin Waibel
• Reporter: Mario Curcija
• Created: 07/Apr/08 10:53
• Updated: 08/Apr/08 11:09

Description

After org.odmg.Transaction.abort() call preceded by org.apache.ojb.odmg.TransactionExt.flush() all objects that were modified during transaction are found in cache.

Expecting:
All modified object should be evicted from cache on abort().

Reproducing:
With 1.0.5RC1 Tests:
org.apache.ojb.odmg.ODMGRollbackTest with ObjectCacheDefaultImpl (with autoSync=false) as Cache Implementation
following two testCases fails:

• testTransactionFlush() and
• testTransactionFlush_2()

Both tests are doing following:

• persisting previously non-persisted objects by invoking
  Transaction.lock(Object, int) and calling TransactionExt.flush()
  afterwards,
• performing Transaction.abort() and at last,
• checking for existence of used objects (in DB/Cache) via
  org.apache.ojb.broker.query.QueryByIdentity expecting not to find them.

Original ojb-user mailing list thread: http://www.mail-archive.com/[e-mail]/msg16156.html