1 Reply Latest reply on Jul 28, 2008 12:21 PM by Brice Ruth

    Bridging WS-TX to JTA, with Spring/Hibernate - who closes th

    Brice Ruth Novice

      Using JBossTS 4.3.0GA with JBoss AS 4.3.0 EAP and the "bridge" (pulled from SVN a while back, not sure if its ever been updated) - I'm seeing a strange, non-fatal error.

      What I'm basically doing is at the entry point to my code (currently a servlet), I'm getting a UserTransaction, then getting the InboundBridge and starting it. Then my code proceeds and when it returns, I stop the bridge and commit the UserTransaction.

      When my code proceeds, it invokes Spring-tx managed Hibernate code, which does some work under JTA with Oracle.

      Everything seems to work fine (data is updated, web service calls are made, ws-tx coordination happens, etc.). But, apparently the local database connection isn't closed. I get the following error and a stacktrace from one of the Hibernate accesses.

      09:39:53,661 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@19ca6bc
      


      So, where is the connection supposed to be closed in this scenario? I'm guessing that since the Spring-tx code joins an existing Tx, that it won't close the connection, right? The connection would need to stay open until the 2PC finished, I believe?

      Any guidance would be appreciated. Thank you.