camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-8241) Exec command failures using Java 8 on Unix
Date Sun, 22 Feb 2015 10:52:11 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-8241.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.14.2)

Thanks for the unit test.

I could reproduce the issue, and added a workaround in camel-exec to catch the stream closed
and move on.

But the bug is in commons-exec which likely need to fix that issue.

> Exec command failures using Java 8 on Unix
> ------------------------------------------
>
>                 Key: CAMEL-8241
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8241
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.14.0
>         Environment: JDK 1.8 on Unix systems
>            Reporter: Dave Heath
>            Assignee: Claus Ibsen
>             Fix For: 2.15.0
>
>         Attachments: CamelExecTest.java
>
>
> I'm attaching a test case that shows an issue I've been running into with the exec command
since updating my environment to Java 8. It appears that I'm running into a race condition
where a stream is sometimes closed prematurely before DefaultExecutor has a chance to close
it, causing DefaultExecCommandExecutor to throw and exit (even though the command did execute
properly). I've tested this against the updated version of commons-exec as well just to make
sure this hasn't somehow been fixed in that library.
> Please note that the attached test doesn't always fail; you may need to run it a few
times before the error will show up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message