[
https://issues.jboss.org/browse/JBWEB-255?page=com.atlassian.jira.plugin....
]
Remy Maucherat commented on JBWEB-255:
--------------------------------------
Hum, yes. I don't think the patch is that good though, since the input stream is
opened in a loop, and closed outside of it. It would need to be nested.
ExtensionValidator does not close inputstream
---------------------------------------------
Key: JBWEB-255
URL:
https://issues.jboss.org/browse/JBWEB-255
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossWeb-2.1.11.GA
Reporter: James Livingston
Assignee: Remy Maucherat
Attachments: jbossweb-extensionvalidator-close.diff
ExtensionValidator.validateExtension() closes the InputStream for the web
application's manifest, but does not do so for the manifests from jar files. This
results in file descriptors being left open until the next garbage collection finalises
them.
While deploying applications with many jar files, this can result in errors because the
file descriptor limit has been reached.
This is already fixed in Tomcat 7, and backporting the patch at
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/java/org/apache/catalin...
is simple.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira