cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31760] - Handle / Semaphore Leak?
Date Thu, 21 Oct 2004 08:23:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31760>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31760

Handle / Semaphore Leak?

michael.straessle@bk.admin.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.1.4                       |2.1.5



------- Additional Comments From michael.straessle@bk.admin.ch  2004-10-21 08:23 -------
similar results with the following environments

a) cocoon 2.1.5 / jetty standalone-demo /sun jdk1.4.2_05 on Win XP Pro
b) cocoon 2.1.5 / jetty standalone-demo /sun jdk1.4.2_06 on Win XP Pro
c) cocoon 2.1.5 / tomcat 5.0.28 /sun jdk1.4.2_05 on Win NT

...so this isssue is not related to tomcat IMO.
number of handles seems directly related to amount of RAM used by the java vm 
(between 10 and 20% of memory used in KB).

garbage collection tuning as mentioned in bug #31116 helps to keep number of 
handles at about 10k with 100MB of RAM used in c), which is my production 
environment. in a) and b), handles will go up to over 20k after having run some 
of the samples (e.g. fop caching).

up to now, I have not found any information that this number of handles is 
critical on NT/2K/XP systems

Mime
View raw message