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.
Hello Gilberto,
we had eexactly this bevaior in our application and asked this mailinglist and
the one of postgres for a solution.
But anyone could help us.
So we developed a really dirty workaround and force a "COMMI"-statement after
all our SELECT-Queries...
Not nice but it solved the probl
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:
While using the application we see that the conn
