It's actually a vendor supplied application. I filed a bug/support request
and they returned with a patch.
I guess I was wondering if there were any jvm startup options I may have
over looked that may help with this sort of issues. But it definitely seems
to be a coding issue.
Thanks,
Chad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chad,
Chad Kellerman wrote:
It's actually a vendor supplied application. I filed a bug/support request
and they returned with a patch.
Were you able to inspect the patch? I'm interested to see what they
chose to do.
I guess I was wondering if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chad,
Chad Kellerman wrote:
To get a better understanding... the application indexes
uploaded files, the indexing process creates the temporary files then
removes them.
Can you share the code that actually does this? The javadoc for
Tomcat Users,
Just wondering if anyone else has run into this problem.
First let's get the specifics out of the way:
Tomcat: 5.5.25
Java: Sun JDK 1.5.0_13
Linux RHEL 5
The Tomcat server is situated on it's own file system, with the applications
on another. I got a page this weekend, saying
From: Chad Kellerman [mailto:[EMAIL PROTECTED]
Subject: Tomcat JVM not releasing deleted files (lsof show
delete inodes taking up disk space)
the application indexes uploaded files, the indexing process
creates the temporary files then removes them.
Sounds like your indexing process
- Original Message -
From: Chad Kellerman [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Monday, September 29, 2008 4:39 PM
Subject: Tomcat JVM not releasing deleted files (lsof show delete inodes
taking up disk space)
Tomcat Users,
Just wondering if anyone else has run
