I might add I am experiencing the same error. I spent quite a bit of time trying to solve this and I am glad I am not the only one experiencing this.
I am using Hibernate 2.1.8 with JBossCache 1.2.1 and Weblogic 8.1. In my case, I have two applications on the same server. App 1 starts the transaction using the Hibernate API setup with a JTA factory, does some queries and then forwards a request to a servlet in app 2. Servlet 2 then starts its own transaction using the Hibernate API (which in reality would join the JTA transaction started in app1) and does some updates and inserts, then commits (which wont really commit yet since App 1 still has the JTA transaction still open). After this control goes back to App1 and it finally commits. At this point, I get an exception similar to the first poster's in App2 (even though I committed in App1, it causes the commit to propogate back to App2). It is also on the UpdateTimestampsCache. I am also using an Oracle XA datasource. (It is almost as if the JBossCache on App2 loses track that it owns the lock on UpdateTimestampsCache in the very same thread, and tries to aquire it again even though it already owns it.) I hope this helps, and would also appreciate any help. Thank you, Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871572#3871572 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871572 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
