hi all,
(especially Bruce, who helped me once or more times in the past ;-))
it's been a while since I post my last message on this forum (probably
not a bad sign ;-)) - serious : kudos to all.
I am on a jdo project again, and have the following scenario (running
test cases)
I create a Database in the TestMain, call begin( ) and hand this
Database instance to a TestCase.
In the TestCase I use the *same* Database instance and execute a Query
(with AccessMode Shared), but I don't change the objects at all, just
check that the ascending mode for timestamp is correct.
everything works fine until the Thread returns to the TestMain again,
where I call the db.commit( ) to commit changes. Suddenly I get a
..... as been modified by a concurrent transaction
at
org.exolab.castor.jdo.engine.SQLEngine.store(SQLEngine.java:867)
at
org.exolab.castor.persist.ClassMolder.store(ClassMolder.java:1584)
at
org.exolab.castor.persist.LockEngine.store(LockEngine.java:758)
exception.
I could circumvent it by setting the AccessMode to ReadOnly, but somehow
it worries me that this happens, even if the Database is the same
instance, and there exist just one call to begin() and commit( ) - so
where does that "concurrent transaction" come from?
I am using castor-0.9.4.1.jar (allthough currently downloadin 4.2 ;-))
thank you very much
-- Jakob
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
