You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Scott Parkerson (JIRA)" <ji...@apache.org> on 2010/05/12 19:37:44 UTC
[jira] Created: (CAMEL-2715) RoutingSlip EIP Seems to Misbehave on
Async targets, even with InOut specified
RoutingSlip EIP Seems to Misbehave on Async targets, even with InOut specified
------------------------------------------------------------------------------
Key: CAMEL-2715
URL: https://issues.apache.org/activemq/browse/CAMEL-2715
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.1.0
Environment: Camel 2.1.0 / Linux / Sun JDK Java 2 SE build 1.6.0_18-b07
Reporter: Scott Parkerson
Attachments: camel-routingslip-testcase.zip
Right now, it seems that it's entirely too easy to create a routing slip EIP that doesn't act like a routing slip at all; if Async InOnly destinations are used, then things do not seem to work (i.e. each destination receives the message).
It seems like the only way to get it to work (and even then, it's not guaranteed) is to set the MEP to {{InOnly}} on the Consuming endpoint. Setting it on the RoutingSlip has no effect.
Furthermore, I'd expect that the Out message on a message returning to the routing slip would be propagated to the in message of the next; this doesn't seem to be happening, or I've screwed up setting the headers to check the breadcrumbs so I can verify order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-2715) RoutingSlip EIP Seems to Misbehave on
Async targets, even with InOut specified
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2715.
--------------------------------
Assignee: Claus Ibsen
Fix Version/s: 2.4.0
Resolution: Working as Designed
trunk: 949128.
See this unit test (JmsRoutingSlipIssueTest.java) for an example of doing routing slip over JMS
http://svn.apache.org/viewvc?rev=949128&view=rev
> RoutingSlip EIP Seems to Misbehave on Async targets, even with InOut specified
> ------------------------------------------------------------------------------
>
> Key: CAMEL-2715
> URL: https://issues.apache.org/activemq/browse/CAMEL-2715
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.1.0
> Environment: Camel 2.1.0 / Linux / Sun JDK Java 2 SE build 1.6.0_18-b07
> Reporter: Scott Parkerson
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
> Attachments: camel-routingslip-testcase.zip
>
>
> Right now, it seems that it's entirely too easy to create a routing slip EIP that doesn't act like a routing slip at all; if Async InOnly destinations are used, then things do not seem to work (i.e. each destination receives the message).
> It seems like the only way to get it to work (and even then, it's not guaranteed) is to set the MEP to {{InOnly}} on the Consuming endpoint. Setting it on the RoutingSlip has no effect.
> Furthermore, I'd expect that the Out message on a message returning to the routing slip would be propagated to the in message of the next; this doesn't seem to be happening, or I've screwed up setting the headers to check the breadcrumbs so I can verify order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-2715) RoutingSlip EIP Seems to Misbehave on
Async targets, even with InOut specified
Posted by "Scott Parkerson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Parkerson updated CAMEL-2715:
-----------------------------------
Attachment: camel-routingslip-testcase.zip
Attached a test case that can be used to examine the issue(s).
> RoutingSlip EIP Seems to Misbehave on Async targets, even with InOut specified
> ------------------------------------------------------------------------------
>
> Key: CAMEL-2715
> URL: https://issues.apache.org/activemq/browse/CAMEL-2715
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.1.0
> Environment: Camel 2.1.0 / Linux / Sun JDK Java 2 SE build 1.6.0_18-b07
> Reporter: Scott Parkerson
> Attachments: camel-routingslip-testcase.zip
>
>
> Right now, it seems that it's entirely too easy to create a routing slip EIP that doesn't act like a routing slip at all; if Async InOnly destinations are used, then things do not seem to work (i.e. each destination receives the message).
> It seems like the only way to get it to work (and even then, it's not guaranteed) is to set the MEP to {{InOnly}} on the Consuming endpoint. Setting it on the RoutingSlip has no effect.
> Furthermore, I'd expect that the Out message on a message returning to the routing slip would be propagated to the in message of the next; this doesn't seem to be happening, or I've screwed up setting the headers to check the breadcrumbs so I can verify order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.