ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13372] - NPE's from StreamPumper
Date Wed, 12 Feb 2003 23:05:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13372>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13372

NPE's from StreamPumper





------- Additional Comments From conor@cortexebusiness.com.au  2003-02-12 23:05 -------
OK, thanks. The Null pointer is actually within BufferedInputStream. The
internal buffer has been freed because the stream has been closed.

This is what I think is happening. When you control-C JBoss, the process gets
killed, closing the stream. However, this happens in a separate thread from the
read operation. When the read operation starts, the stream is open, but by the
time the buf gets to be used, the stream has been closed and the NPE results.
This sequence bypassses the stream's check to ensure it is open. This is why the
results vary - it depends on the timing of events between two thread.

I will change the IOException catch to an Exception catch which should take care
of this situation.

Mime
View raw message