I don't see anything wrong with your configuration, except one comment: unless 
you are running distributed databases, you really don't need XADataSource, just 
DataSource is fine.  That might save you some troubles, in case your JDBC 
driver has bugs in connection handling for 'multi-database' setup (I am not 
familiar with postgresql).
 
Again, the result of CMP failure does not mean CMP is the cause of connection 
leaks.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tim Riley
Sent: Tuesday, February 27, 2007 9:34 AM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] CMP 2.1 Relationship Not Closing Connections



Hrmmm

Maybe I have resin configured wrong then, because this did not occur in resin 
2.1.17 would you mind taking a look?

 

resin.conf

 

<host id="" root-directory="/usr/local/base/web">

...

      <database>

         <jndi-name>jdbc/appp</jndi-name>

         <driver type="org.postgresql.Driver">

            <url>jdbc:postgresql://localhost:5432/appp</url>

            <user>xxxxxx</user>

            <password>xxxxxx</password>

         </driver>

         <prepared-statement-cache-size>8</prepared-statement-cache-size>

         <max-connections>20</max-connections>

         <max-idle-time>30s</max-idle-time>

      </database>

      <web-app id="appp" document-directory="/usr/local/base/web/appp/">

        <ejb-server>

           <jndi-name>java:comp/env/appp</jndi-name>

           <data-source>java:comp/env/jdbc/appp</data-source>

           <config-directory>/usr/local/feds/web/appp/WEB-INF</config-directory>

        </ejb-server>

      </web-app>

 

</host>

 

web.xml

<webapp>

...

  <resource-ref>

    <res-ref-name>jdbc/appp</res-ref-name>

    <res-type>javax.sql.XADataSource</res-type>

    <res-auth>Container</res-auth>

  </resource-ref>

 

</webapp>

 

The following keeps occurring in my logs

[12:16:04.439] Closing dangling connections.  All connections must have a 
close() in a finally block.

[12:16:04.517] java.lang.IllegalStateException: Connection [EMAIL PROTECTED] 
was not closed. Connections must have a close() in a finally block.

[12:16:04.517]  at 
com.caucho.jca.UserTransactionImpl.abortTransaction(UserTransactionImpl.java:497)

[12:16:04.517]  at 
com.caucho.jca.UserTransactionProxy.abortTransaction(UserTransactionProxy.java:183)

[12:16:04.517]  at 
com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:193)

[12:16:04.517]  at 
com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:229)

[12:16:04.517]  at 
com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:274)

[12:16:04.517]  at 
com.caucho.server.port.TcpConnection.run(TcpConnection.java:511)

[12:16:04.517]  at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520)

[12:16:04.517]  at com.caucho.util.ThreadPool.run(ThreadPool.java:442)

[12:16:04.517]  at java.lang.Thread.run(Thread.java:595)

[12:16:40.445] Closing dangling connections.  All connections must have a 
close() in a finally block.

 

I would appreciate any help or guidance you could provide.

 

Thanks

Tim


  _____  


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Zhu
Sent: Tuesday, February 27, 2007 12:16 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] CMP 2.1 Relationship Not Closing Connections

 

Most likely the other parts of your code are leaking the DB connections. CMP is 
not likely the source of leak.

We use CMPs extensively, our site is stable, with an over $10 million worth of 
single day on-line transactions.

We are currently running resin 3.0.22.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tim Riley
Sent: Tuesday, February 27, 2007 8:39 AM
To: resin-interest@caucho.com
Subject: [Resin-interest] CMP 2.1 Relationship Not Closing Connections

My name is Tim Riley and I currently upgrading from 2.1.17 to 3.0.23 and I use 
CMP 2.1 (EJB 2). I do not want to upgrade from EJB 2 to EJB 3 however I ran 
into this issue http://bugs.caucho.com/bug_view_page.php?bug_id=1286. Does 
anyone know if there is a work around to this issue or if it is planned to be 
fixed in an up coming release. I am also using Postgresql 8.1.

 

Thanks

Tim

_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to