On 9/10/07, Gilberto C Andrade <[EMAIL PROTECTED]> wrote:
> Michael Gentry wrote:
> > Yeah, that doesn't really surprise me, either. You didn't restart
> > JBoss, did you?
>
> Yes! After that we did an undeploy e deploy of the app.
> But it didn't matter as you could see!
You completely terminate
Michael Gentry wrote:
> Yeah, that doesn't really surprise me, either. You didn't restart
> JBoss, did you?
Yes! After that we did an undeploy e deploy of the app.
But it didn't matter as you could see!
>
> /dev/mrg
>
>
> On 9/10/07, Gilberto C Andrade <[EMAIL PROTECTED]> wrote:
>> Michael Ge
Yeah, that doesn't really surprise me, either. You didn't restart
JBoss, did you?
/dev/mrg
On 9/10/07, Gilberto C Andrade <[EMAIL PROTECTED]> wrote:
> Michael Gentry wrote:
> > It sounds like when JBoss does the redeploy, it isn't actually fully
> > releasing the old application and therefore t
Michael Gentry wrote:
> 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 happens even when we undeploy de webapp!
Other thing shouldn't cayen
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.
solved the problem.
Oilid
> -Ursprüngliche Nachricht-
> Von: Gilberto C Andrade [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 6. September 2007 17:32
> An: user@cayenne.apache.org
> Betreff: Postgresql 8.2 and cayenne 2.0.3 - idle connections
>
> Hi all!
>
>
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
