[jboss-jira] [JBoss JIRA] Resolved: (JBVFS-157) InputStream not closed properly
Ales Justin (JIRA)
jira-events at lists.jboss.org
Mon May 17 11:26:07 EDT 2010
[ https://jira.jboss.org/browse/JBVFS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ales Justin resolved JBVFS-157.
-------------------------------
Fix Version/s: 2.2.0.Alpha3
3.0.0.CR6
Resolution: Done
> InputStream not closed properly
> -------------------------------
>
> Key: JBVFS-157
> URL: https://jira.jboss.org/browse/JBVFS-157
> Project: JBoss VFS
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.1.3.SP1
> Reporter: Martin Putz
> Assignee: Ales Justin
> Fix For: 2.2.0.Alpha3, 3.0.0.CR6
>
>
> A hot-deployed *-service.xml file on EAP 5 is locked on Windows.
> Root cause for this issue is that the InputStream is not closed properly, as Alexey discovered:
> "Apparently, when InputSource is passed in, the parser calls getSystemId(), getByteStream() and getCharacterStream() on it regardless whether any of the methods invoked previously returns non-null value. Then it uses one of the streams returned and closes just the it has used.
> In our impl getCharacterStream() returns wrapped result from getByteStream(). And getByteStream() opens a new stream on each invocation."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list