Armin Waibel wrote:
There is 1 consistent failure:
testIterateWithoutTx Failure expected:<47> but was:<45>
at org.apache.ojb.odmg.DListTest.testIterateWithoutTx(DListTest.java:310)
I will try to debug and get some more info re this.
I think this could be again a sorting problem of returned result set. Think we have to improve the test to compare the "right" objects.
Will do this ASAP.
It might also be an inter-dependency issue among the testcases.
If I run only DListTest it passes:
ant -Dojb.testsToRun=org/apache/ojb/odmg/DListTest.java junit-no-compile-no-prepare-selected
I checked in a new version of this test which take care of sorting problem. Give it a try.
OJB needs at least one primary key attribute for class:
objectTopLevelClass=org.apache.ojb.odmg.LockingMultithreadedTest$LockObjectobjectRealClass=org.apache.ojb.odmg.LockingMultithreadedTest$LockObjectpkValues=null
object to identify: [EMAIL PROTECTED] at org.apache.ojb.broker.Identity.createException(Identity.java:391)
I think this is the nasty concurrency bug. I can't find out where it occur. Some times it seems that the PK field isn't populated when the Identity object was created. I'm stumped!
Seems resonable, it is occuring only at random.
hmm, I will create a jira issue and if this error message occur again, please add your stack trace to jira. Maybe we can isolate the problem this way.
Armin
Regards, Martin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
