[
https://issues.apache.org/jira/browse/CAMEL-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976953#comment-14976953
]
Daniel Davis edited comment on CAMEL-8241 at 10/27/15 7:18 PM:
---------------------------------------------------------------
I can confirm the same error on RHEL 6.x using ServiceMix 5.5.0, Camel 2.15.2
and Oracle Java 1.8_66. The source code for the exec component in branch
camel-2.15.x has the workaround described above.
The stack trace is:
2015-10-27 14:39:58,830 | WARN | ora.apim.update] | EndpointMessageListener
| 124 - org.apache.camel.camel-core - 2.15.2 | Execution of JMS message
listener failed. Caused by: [org.apache.camel.component.exec.ExecException -
Unable to execute command ExecCommand [args=[-f,
staging/ID-oris-srv03-si-edu-51333-1445886844310-7-158], executable=rm,
timeout=9223372036854775807, outFile=null, workingDir=null,
useStderrOnEmptyStdout=false]]
org.apache.camel.component.exec.ExecException: Unable to execute command
ExecCommand [args=[-f, staging/ID-oris-srv03-si-edu-51333-1445886844310-7-158],
executable=rm, timeout=9223372036854775807, outFile=null, workingDir=null,
useStderrOnEmptyStdout=false]
at
org.apache.camel.component.exec.impl.DefaultExecCommandExecutor.execute(DefaultExecCommandExecutor.java:102)[230:org.apache.camel.camel-exec:2.15.2]
at
org.apache.camel.component.exec.ExecProducer.process(ExecProducer.java:53)[230:org.apache.camel.camel-exec:2.15.2]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[124:org.apache.camel.camel-core:2.15.2]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[124:org.apache.camel.camel-core:2.15.2]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[124:org.apache.camel.camel-core:2.15.2]
was (Author: davisda):
I can confirm the same error on RHEL 6.x using ServiceMix 5.5.0, Camel 2.15.2
and Oracle Java 1.8_66. The source code for the exec component has the
workaround described above.
The stack trace is:
2015-10-27 14:39:58,830 | WARN | ora.apim.update] | EndpointMessageListener
| 124 - org.apache.camel.camel-core - 2.15.2 | Execution of JMS message
listener failed. Caused by: [org.apache.camel.component.exec.ExecException -
Unable to execute command ExecCommand [args=[-f,
staging/ID-oris-srv03-si-edu-51333-1445886844310-7-158], executable=rm,
timeout=9223372036854775807, outFile=null, workingDir=null,
useStderrOnEmptyStdout=false]]
org.apache.camel.component.exec.ExecException: Unable to execute command
ExecCommand [args=[-f, staging/ID-oris-srv03-si-edu-51333-1445886844310-7-158],
executable=rm, timeout=9223372036854775807, outFile=null, workingDir=null,
useStderrOnEmptyStdout=false]
at
org.apache.camel.component.exec.impl.DefaultExecCommandExecutor.execute(DefaultExecCommandExecutor.java:102)[230:org.apache.camel.camel-exec:2.15.2]
at
org.apache.camel.component.exec.ExecProducer.process(ExecProducer.java:53)[230:org.apache.camel.camel-exec:2.15.2]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[124:org.apache.camel.camel-core:2.15.2]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[124:org.apache.camel.camel-core:2.15.2]
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[124:org.apache.camel.camel-core:2.15.2]
> 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.14.2, 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)
