I also experienced database "crashes" due to "Too many connections". We solved our problem simply using Tomcat Database Connection Pool and changing a bit our code. You can find information at http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations Hope it helps somebody! Steva
----- Original Message ----- From: "Danny" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Wednesday, January 14, 2004 2:41 PM Subject: AW: [J1 LEAKS ?] RE: jetspeed process and memory leak I don't know what you mean with long time, but the only troubles we have are database-related. Sometimes the portal breaks due to "Too many connections". ...and even this could be our fault. We NEVER experienced any problems with memory leaks, and we have 2 different Jetspeed based projects running - one for over a year and a second one over 3-4 months (with restarts due to updates of course, not without break). Although we have less then 1000 users, I think Jetspeed is quite stable it this concerns. Danny > -----Urspr�ngliche Nachricht----- > Von: Pernoud Aurelien [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 14. Januar 2004 14:36 > An: Jetspeed Users List > Betreff: [J1 LEAKS ?] RE: jetspeed process and memory leak > > > > Paul Mansfield a �crit : > > > > typically, I tried a random variation of my searches on google and > > came up with an answer: > > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg 111708.html > > these suggest that tomcat itself causes memory leaks, and is > exacerbated by jetspeed's leaks. I've just read this mail and see this : > From: William Connor > Subject: Re: Tomcat 4.0.x memory leak (not javac) > Date: Wed, 03 Dec 2003 09:09:37 -0800 > > We first ran into this bug when hot-deploying JetSpeed - about seven > times would cause an out of memory w/ the default heap size. > JetSpeed had so many leaks itself that we dropped down to bares bones > test app with a servlet, but no JSPs or third party libraries. Jetspeed has so many leaks ??? We've made some tests over here for potential leak and didn't find anything alarming. The only stuff that was potentially leaking was the Tool object from velocity, staying in memory even after a request is done, we didn't really understand how to use it so we plan not to use it anymore. Did anyone ever really meet those memory leak, or is it more the portlets developped by a end-user that could leak... ? That's just cause I was a little afraid of those lines, but already seen so many people yelling at opensource projects saying it was leaking where it wasn't that I'd like any end-user real experience. Tell me someone already had a jetspeed portal running for a long time ??? :) Aurelien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
