You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2008/10/11 02:23:52 UTC
[jira] Created: (CAMEL-974) DataSetSedaTest intermittent test
failure
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.
[jira] Commented: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46447#action_46447 ]
Jonathan Anstey commented on CAMEL-974:
---------------------------------------
Hadrian, yeah, we don't want to just mask the problem :) I just remember having this issue in routes that did not have any seda endpoint
See: http://svn.apache.org/repos/asf/activemq/trunk/activemq-camel-loadtest/src/test/resources/org/apache/activemq/soaktest/LoadTest-context.xml
In that route, removing the produceDelay (which will then default it to 3 ms) will cause the same problem you see in DataSetSedaTest.
> 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.
[jira] Updated: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-974:
------------------------------
Priority: Minor (was: Major)
Fix Version/s: (was: 2.0.0)
Future
> 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
> Priority: Minor
> Fix For: Future
>
>
> 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.
[jira] Resolved: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-974.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
2.0.0
Assignee: Claus Ibsen
DataSet expects the data to receive in order, but the seda is async so some exchanges can arrive out of order.
I have added the produceDelay to the unit test and fixed the seda consumer to not minimum sleep for 4 millis.
trunk: 766288
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> 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.
[jira] Commented: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46377#action_46377 ]
Claus Ibsen commented on CAMEL-974:
-----------------------------------
I do think there were some high concurrency issue with the seda component. Willem fixed a problem with copying exchanges, but I used once in a while to get such errors as well.
But not for 2+ months or so.
See also CAMEL-901 that somehow could be related
If you change it to use direct queues then I am sure it works all the time.
> 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.
[jira] Commented: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46443#action_46443 ]
Jonathan Anstey commented on CAMEL-974:
---------------------------------------
You can also slow down the dataset producer by adding produceDelay=numOfMilliseconds. The default is 3 (milliseconds) but maybe this is not large enough?
> 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.
[jira] Commented: (CAMEL-974) DataSetSedaTest intermittent test
failure
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ 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.