It sounds like when JBoss does the redeploy, it isn't actually fully releasing the old application and therefore the connection count will keep going up in your database until you restart JBoss. This could be a good argument for you to use JBoss's connection pools for your production deployment. This page discusses how to use a JNDI-provided connection pools from the container (even if not JBoss-specific):
http://cayenne.apache.org/doc20/using-jndi.html Hope that helps some ... /dev/mrg On 9/6/07, Gilberto C Andrade <[EMAIL PROTECTED]> wrote: > Hi all! > > After following some tips from here: > http://article.gmane.org/gmane.comp.java.cayenne.user/8360, we finally > put our webapp in production: > > server: jboss-4.0.2 > server: postgresql 8.2 > > PesquisaDataDominioNode.driver.xml: > > <?xml version="1.0" encoding="utf-8"?> > <driver project-version="2.0" class="org.postgresql.Driver"> > <url value="jdbc:postgresql://hostname:5432/bcoproducao"/> > <connectionPool min="5" max="10" /> > <login userName="pesquisa_user" password="senha"/> > </driver> > > While using the application we see that the connections are superior > than max=10. But this haven't caused any problem. > > So, after one second deploy (I think is redeploy) on jboss we see that > those opened idle connections (about 30) stay there without been used > and when the app starts we see new connections(5) which are used. > > Did anyone have seen this behavior before? > > Thanks for any tip! > > Gilberto > www.secad.to.gov.br
