[
https://issues.apache.org/jira/browse/EXEC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664028#action_12664028
]
joehni edited comment on EXEC-33 at 1/14/09 11:44 PM:
--------------------------------------------------------------
{quote}
As the mentioned Sun issues point out, Thread.interrupt() doesn't help either
once the blocking call to read() has been made.
{quote}
This is actually not completely true. It depends on the implementation of the
JVM and the underlaying platform. On Solaris read() will be interrupted and
throwing an InterruptedIOException. So be prepared to deal with both situations.
was (Author: joehni):
{quote}
As the mentioned Sun issues point out, Thread.interrupt() doesn't help either
once the blocking call to read() has been made.
{quote}
This is actually not completely true. It depends on the implementation of the
JVM and the underlaying platform. On Solaris read will be interrupted and read
throws an InterruptedIOException. So be prepared to deal with both situations.
> PumpStreamHandler hangs if System.in is redirect to process input stream
> ------------------------------------------------------------------------
>
> Key: EXEC-33
> URL: https://issues.apache.org/jira/browse/EXEC-33
> Project: Commons Exec
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Windows Vista
> Reporter: Marco Ferrante
> Assignee: Siegfried Goeschl
> Priority: Minor
>
> When process input is redirected using a PumpStreamHandler, e.g.
> PumpStreamHandler streamHanlder = new PumpStreamHandler(out, err,
> System.in);
> exec.setStreamHandler(streamHanlder);
> MockExecuteResultHandler handler = new MockExecuteResultHandler();
> exec.execute(cl, handler);
> the process hangs and never exit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
