[jboss-jira] [JBoss JIRA] Updated: (JBVFS-157) InputStream not closed properly
[
https://jira.jboss.org/jira/browse/JBVFS-157?page=com.atlassian.jira.plug...
]
Martin Putz updated JBVFS-157:
------------------------------
Summary: InputStream not closed properly (was: InputStreams not close)
Description:
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."
Assignee: Ales Justin (was: John Bailey)
InputStream not closed properly
-------------------------------
Key: JBVFS-157
URL: https://jira.jboss.org/jira/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
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira