commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36545] - [exec] potential threading issue when closing process.getInputStream()
Date Fri, 09 Sep 2005 11:33:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36545>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36545


jerome@coffeebreaks.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3




------- Additional Comments From jerome@coffeebreaks.org  2005-09-09 13:33 -------
Ah yes. My bad. It seems like I didn't correctly read the latest commons-exec
code, I missed the stop() implementation in the PumpStreamHandler class.

So the problem appears to be CruiseControl only and this issue can be closed.

Note: the javadoc for the ExecuteStreamHandler.stop() method should probably say
that implementing classes must empty the streams properly, otherwise there will
could be hangs. I live the issue opened for that reason only, decreasing
priority/severity. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message