I was wondering if anyone can suggest any reason for my problems.

Platform:
- rh 7.3 with kernel 2.4.20
- j2sdk 1.4.2_01
- apache 1.3.28
- tomcat 5.0.16 (upgraded yesterday from 5.0.12, no change)
- jetspeed 1.4 release versio

When I start up tomcat, I end up with 77 j2sdk processes each 61M
(according to top).

If I then reload my webapps using the tomcat manager webpage, the number
of processes immediately grows to 100 (not always the same amount), and
eat another 8 or 9MB of memory! It's not the stopping, which has no
effect, but the starting, which eats resources.

We have found that jdbc is very bad at releasing resources 
automatically, you have to be very strict in closing everything after
use, but our app isn't really that big - about five portlets with
back-end database links to mysql and oracle. Surely if the app is
stopped then a lot of memory should be released?

thanks for taking the time to read this,
Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to