Jon,
Jon Wilmoth wrote:
I've opened http://jira.codehaus.org/browse/CASTOR-2269 for the
release to include the JDO source/javadocs.
Thank you. I should be able to .. resolve this in a minimal time.
Ok...maybe asking the question from another angle will help...are
there any simple requirements that must be satisfied for a read-only
query to obtain a read lock? Is a read lock supposed to be required
for a read-only query?
Not that I know. But having a detailed look at the sources might reveal
some knowledge I don't have top of my head. Just for completeness: how
are you running the 'read-only' query ? And how about the entities that
are referenced by that query ? Are any/all of these declared to be
read-only or read-write per the mapping file ?
----- Original Message ---- From: Werner Guttmann
<[EMAIL PROTECTED]> To: [email protected] Sent: Monday,
January 21, 2008 2:14:26 PM Subject: Re: [castor-user] Causes of
IllegalStateException: Transaction
org.castor.persist.LocalTransactionContext does not hold the read
lock during Query?
Jon,
Jon Wilmoth wrote:
Hi Werner,
I followed the link on the main www.castor.org page to
http://dist.codehaus.org/castor/1.1.2.1/. The
castor-1.1.2.1-src.zip file doesn't contain the JDO code (e.g.
org.exolab.castor.persist.LockEngine) which is called out in my
stacktrace.
Oops, that's bad. Can you please open a new Jira issue and we'll act
upon it in due time ?
I'll take a look at the source...any "easy" reasons for
the exception being thrown?
No, not really .. :-(. Which is not what you wanted to hear, I guess.
Thanks, Jon ----- Original Message ---- From: Werner Guttmann
<[EMAIL PROTECTED]> To: [email protected] Sent:
Monday, January 21, 2008 1:53:24 PM Subject: Re: [castor-user]
Causes of IllegalStateException: Transaction
org.castor.persist.LocalTransactionContext does not hold the read
lock during Query?
Jon,
trying to addres things one by one.
Werner Jon Wilmoth wrote:
I'm getting the following error while trying to run a read-only
query. I haven't been able to do much research of my own since
the 1.1.2.1 release I'm using doesn't have the JDO source
available (or the related javadocs). The object I'm trying to
query has a collection property of other another castor mapped
object as well as two other 1-to-1 properties to other castor
mapped objects. None of those properties are being explicitely
loaded and all castor mapped properties are marked as lazy="true"
in the castor mappings. Any pointers on what might cause a
read-only query to fail like this are appreciated. On a related
note, can the release process include the JDO source and
javadocs?
The sources for the 1.1.2.1 are available and always have been
available at
http://repository.codehaus.org/org/codehaus/castor/castor-jdo/1.1.2.1/
Having said that, it looks like you are looking somewhere else.
Where, if I may ask ?
Finally can the current release be reposted with JDO source and
javadocs?
Caused by: java.lang.IllegalStateException: Transaction
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> does
not hold the read lock:
com.apex.mytracker.app.workout.WorkoutExercise/<1(1)>/0 -/-! at
org.exolab.castor.persist.LockEngine$TypeInfo.assure(LockEngine.java:1353)
at
org.exolab.castor.persist.LockEngine$TypeInfo.access$600(LockEngine.java:1102)
at
org.exolab.castor.persist.LockEngine.preStore(LockEngine.java:766)
at
org.castor.persist.AbstractTransactionContext.prepare(AbstractTransactionContext.java:1198)
at
org.exolab.castor.jdo.engine.LocalDatabaseImpl.commit(LocalDatabaseImpl.java:169)
at
com.apex.mytracker.app.AbstractBusinessObject.releaseDatabase(AbstractBusinessObject.java:116)
at
com.apex.mytracker.app.AbstractBusinessObject.handleOQLQueryResults(AbstractBusinessObject.java:675)
at
com.apex.mytracker.app.AbstractBusinessObject.executeFind(AbstractBusinessObject.java:590)
at
com.apex.mytracker.app.AbstractBusinessObject.internalFindByProperties(AbstractBusinessObject.java:525)
Thanks,
Jon
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
