commons-fileupload new implementation 1.6.0+ doesn't release file resources automatically any more due to an internal change inside commons-fileupload to use Java NIO...
Using commons-fileupload 1.6.0 for us brought on a major production outage across multiple servers where the system runs out of file descriptors, and rolling back to 1.5.0 remediated the issue.
The issue was reported to commons-fileupload as https://issues.apache.org/jira/browse/FILEUPLOAD-368 and given the detail in the ticket there, it appears that the matter has been narrowed down to an internal change in commons-fileupload which now makes it critical that applications explicitly close resources rather than relying on them being auto-closed. The wording in the ticket there indicates they are considering the matter a feature, not a bug, something for users of commons-fileupload to deal with explicitly.
This may well have impact on WComponent's use of commons-fileupload, drawing to your attention.
commons-fileupload new implementation 1.6.0+ doesn't release file resources automatically any more due to an internal change inside commons-fileupload to use Java NIO...
Using commons-fileupload 1.6.0 for us brought on a major production outage across multiple servers where the system runs out of file descriptors, and rolling back to 1.5.0 remediated the issue.
The issue was reported to commons-fileupload as https://issues.apache.org/jira/browse/FILEUPLOAD-368 and given the detail in the ticket there, it appears that the matter has been narrowed down to an internal change in commons-fileupload which now makes it critical that applications explicitly close resources rather than relying on them being auto-closed. The wording in the ticket there indicates they are considering the matter a feature, not a bug, something for users of commons-fileupload to deal with explicitly.
This may well have impact on WComponent's use of commons-fileupload, drawing to your attention.