|
From: <jue...@we...> - 2004-03-31 14:37:44
|
BTW, Colin, is the JTA/Hibernate resource management issue completely = resolved for you now? Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Colin Sampaleanu Sent: Wednesday, March 31, 2004 4:25 PM To: spr...@li... Subject: Re: [Springframework-developer] Re: [springframework - Help] RE: Connection error using Spring/Hibernate/JBoss 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 = this? 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/Hibernate/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 = called on >a local tx. Use of local transactions on a jta transaction with more = than one >branch may result in inconsistent data in some cases of failure. > =20 > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Colin S. <col...@ex...> - 2004-03-31 15:12:05
|
As far as I can tell all is ok. Now to tell you the truth, the only=20 reason it was ever happening for me is that due to something being=20 misconfigured; a tx was not rolling back on a checked exception, so=20 commit was still being called on a Hibernate Session that had thrown an=20 exception, which caused a flush to happen at that inopportune time. My=20 current code would now never get that far. But from what I remember I=20 switched over to the fixed Spring code before I reworked my code, and=20 all was ok... j=FCrgen h=F6ller [werk3AT] wrote: >BTW, Colin, is the JTA/Hibernate resource management issue completely re= solved for you now? > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Colin Sampaleanu >Sent: Wednesday, March 31, 2004 4:25 PM >To: spr...@li... >Subject: Re: [Springframework-developer] Re: [springframework - Help] >RE: Connection error using Spring/Hibernate/JBoss > > >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: > > =20 > >>Colin, >> >>I remember you had similar problems a while ago. What's your take on th= is? Can you recheck the issue? >> >>Juergen >> >> >>________________________________ >> >>Von: SourceForge.net [mailto:no...@so...] >>Gesendet: Mi 31.03.2004 02:54 >>An: no...@so... >>Betreff: [springframework - Help] RE: Connection error using Spring/Hib= ernate/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 suc= h as... >> >> >>2004-03-30 19:37:32,359 [Thread Pool Worker-7] WARN >>org.jboss.resource.connectionmanager.TxConnectionManager - Prepare call= ed on >>a local tx. Use of local transactions on a jta transaction with more th= an one >>branch may result in inconsistent data in some cases of failure. >> =20 >> |