You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Adam Bender (JIRA)" <ji...@apache.org> on 2009/10/22 01:08:59 UTC
[jira] Updated: (WICKET-2534) File Handle Leak in URLResourceStream
[ https://issues.apache.org/jira/browse/WICKET-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Bender updated WICKET-2534:
--------------------------------
Attachment: UrlResourceStream.java
This file contains the workaround described here:http://www.mail-archive.com/wicket-user@lists.sourceforge.net/msg20951.html and is identical to the code used in URLResourceStream#lastModifiedTime
> File Handle Leak in URLResourceStream
> -------------------------------------
>
> Key: WICKET-2534
> URL: https://issues.apache.org/jira/browse/WICKET-2534
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.1, 1.4.2, 1.4.3
> Environment: Any
> Reporter: Adam Bender
> Attachments: UrlResourceStream.java
>
>
> The URLResourceStream constructor is using a UrlConnection to access the lastModifiedDate of jar files. This leads to a known File Handle leak as described here: http://www.mail-archive.com/wicket-user@lists.sourceforge.net/msg20951.html . The workaround for this issue is also described here. It appears that this workaround has been applied to the URLResourcesStream#lastModifiedTime method and so it could easily be replicated in the constructor to avoid calling lastModifiedTime on the JarUrlResourceConnection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.