[
https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46444#action_46444
]
Hadrian Zbarcea commented on CAMEL-974:
---------------------------------------
@Claus, I saw that mail exchange, but didn't look into it, since you were on
top of it :)
@Jon, well, the question is if there is some subtle problem in the seda
component, of course we can work it around.
It doesn't happen often, it never happens in eclipse, i didn't see it if i
enable logging, it's definitely some timing issue.
> DataSetSedaTest intermittent test failure
> -----------------------------------------
>
> Key: CAMEL-974
> URL: https://issues.apache.org/activemq/browse/CAMEL-974
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.4.0
> Reporter: Hadrian Zbarcea
> Fix For: 2.0.0
>
>
> I get this kind of failures in the DataSetSedaTest now and then:
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.731 sec <<<
> FAILURE!
> test(org.apache.camel.component.dataset.DataSetSedaTest) Time elapsed: 4.49
> sec <<< ERROR!
> java.lang.AssertionError: dataset:foo Failed due to caught exception:
> java.lang.AssertionError: Header: camelDataSetIndex does not match. Expected:
> 33 but was: 32 on Exchange[Message: <hello>world!</hello>] with headers:
> {camelDataSetIndex=32}
> at
> org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:712)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:255)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:214)
> at
> org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:141)
> at
> org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:283)
> at
> org.apache.camel.component.dataset.DataSetSedaTest.test(DataSetSedaTest.java:35)
> I am not sure yet if it's just a test issue (quite probable) or there's a
> more serious underlying issue. If anybody else experienced this please add a
> comment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
