|
From: Colin S. <col...@ex...> - 2004-03-31 14:24:52
|
The issue I had was that sometimes JBoss would complain about having to=20 release a connection for me. Additionally, I earlier had some cases=20 where it said it didn't know the connection I was trying to release. I=20 did a fair amount of tracing through our whole code when this was=20 happeing, and am almost 100% sure it's a jboss problem. This is=20 corroborated by the fact that the problem was _much_ worse in JBoss=20 3.2.2RC3 than in the current 3.2.3 I am using. As of a few weeks ago I=20 actually got rid of all EJBs except for a message driven bean which is=20 still around, and I still seem to get the complaint releasing the=20 connection for me, in some cases, as far as I know (have to verify this=20 completely). So I don't think this is quite the same issue. I was going a lot of mix=20 and matching of CMT and Spring, and never got the warning below. I will=20 follow up on the post below... j=FCrgen h=F6ller [werk3AT] wrote: >Colin, >=20 >I remember you had similar problems a while ago. What's your take on thi= s? Can you recheck the issue? >=20 >Juergen >=20 > >________________________________ > >Von: SourceForge.net [mailto:no...@so...] >Gesendet: Mi 31.03.2004 02:54 >An: no...@so... >Betreff: [springframework - Help] RE: Connection error using Spring/Hibe= rnate/JBoss > > > > >Read and respond to this message at: >https://sourceforge.net/forum/message.php?msg_id=3D2499567 >By: pgmjsd > >Bad news I'm afraid. > >Hibernate 2.1.2 + Spring 1.0 + JBoss CMT results in *many* warnings such= as... > > >2004-03-30 19:37:32,359 [Thread Pool Worker-7] WARN >org.jboss.resource.connectionmanager.TxConnectionManager - Prepare calle= d on >a local tx. Use of local transactions on a jta transaction with more tha= n one >branch may result in inconsistent data in some cases of failure. > =20 > |