You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2005/09/28 15:08:12 UTC

DO NOT REPLY [Bug 36843] New: - NativeHeap saturation with DeleteOnExit

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=36843>.
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=36843

           Summary: NativeHeap saturation with DeleteOnExit
           Product: Commons
           Version: 1.0.2
          Platform: Other
        OS/Version: AIX
            Status: NEW
          Severity: critical
          Priority: P1
         Component: File Upload
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: alain.duval1@mpsa.com


In a long running jvm (ie: application on WEBSPHERE Application server), use of 
FileUpload (DefaultFileItem.gettempfile) consume native heap via DeleteOnExit
when running request in multi-part data with STRUTS. 

We got some crash due to native heap saturation (512 MO Max of Heap Native when 
running with 2G0 Heap and memory model specific to IBM JVM 1.3). 

Only workaroud for us are:
-Reducing use of DefaultFileItem.getTempFile in application
-Stop / Restart Application Server every night

Same problem not already solve (since 2001) at SUN Bug database
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4513817

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org