Goodmorning all,
We updated to Castor-0.9.9, with java 1.5.0_5.
We're starting to see this exception in ClassMolder.load (which I
understand was recently heavily modified etc):
java.lang.ArrayIndexOutOfBoundsException: 15
at org.exolab.castor.persist.ClassMolder.load(ClassMolder.java:625)
at org.exolab.castor.persist.LockEngine.load(LockEngine.java:368)
at
org.castor.persist.TransactionContext.load(TransactionContext.java:713)
at org.exolab.castor.persist.QueryResults.fetch(QueryResults.java:232)
at
org.exolab.castor.jdo.engine.OQLQueryImpl$OQLEnumeration.hasMore(OQLQueryImpl.java:584)
at
org.exolab.castor.jdo.engine.OQLQueryImpl$OQLEnumeration.hasMore(OQLQueryImpl.java:567)
at
au.com.mpl.xeder.entity.DBObjectFactory.OQLFetchObjectList(DBObjectFactory.java:364)
I'm currently putting together a test case for this, but its fairly
complex so it might take me a while (time constraints and so forth).
The worst bit is that the problem appears to be fairly random, so it might
something to do with our locking modes.. also the part where it happens
might sometimes result in us hitting the castor code to load certain
components (in the same thread) fairly rapidly (but always in the
read-only mode). (although they will be made using the OQL query, rather
then db.load).
Any ideas? Been through the JIRA, found a couple of older entries that
might be related, but doubtful if its been rewritten.
then again, it could just be the way we are using castor as well ;) hard
to say.
Has anyone else seen this issue?
Cheers;
--
//chris
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
