So first off, apologies for the double post. My initial post had a bad subject line, and at this point, I think has been relegated to the netherworld known as "page 2". I'm hoping a more descriptive subject will help, and if not, I promise, no triple posts.
I'm a veteran Hibernate user, but this one's got me stumped. I have entities and their collections all set up in JPA (on JBoss 4.2.3) with @Cache annotations, all with appropriate regions specified. I also have their respective collections marked with @Cache and appropriate regions specified.
Everything worked fine until I put @BatchSize on two collections on one of my entities. Suddenly I get this error:
Code:
org.hibernate.cache.CacheException: org.jboss.cache.lock.TimeoutException failure acquiring lock: fqn=/, caller=Thread[ajp-###.###.###.###-####-7,5,jboss], lock=read owners=[GlobalTransaction:<###.###.###.###:####>:18] (org.jboss.cache.lock.LockStrategySerializable@6c9d476e)
The moment I take either the @BatchSize annotation, or the @Cache annotation of one of the two collections, everything works fine. But what's with the "fqn=/" . . . one collection is for region "campaign/nodes" the other is region "campaign/connections".
Similarly, when I turn on the query cache, if I run more than one cacheable query in the same session, I get the SAME error . . . again with "fqn=/" even though I'm specifying "query/userByUsername" and "query/simpleCampaign" for the respective query cache regions.
I've tried tracing the code, and I can dig further if I need to, but I'm hoping someone has a quick "off the top of the head" answer for me. Something dumb I'm doing.
Oh, and when I turn the cache isolation level down to REPEATABLE_READ, all hell breaks loose . . . phantoms EVERYWHERE. It's gotta be something with how the cache is working.
Any help is appreciated.
Thanks.
-Falken