[
https://issues.apache.org/activemq/browse/CAMEL-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2755.
--------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
trunk: 948686.
> VM endpoints with same name do not communicate if args don't match
> ------------------------------------------------------------------
>
> Key: CAMEL-2755
> URL: https://issues.apache.org/activemq/browse/CAMEL-2755
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.2.0
> Environment: JDK 1.6 using Spring 2.5.6 to start camel contexts
> Reporter: Nathan Jensen
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
>
> If you send to a VM endpoint from one route and consume from the same
> endpoint in another route, but include an argument on only one of the routes,
> Camel sees them as two different routes. Therefore, the messages are never
> consumed. For example:
> <camelContext id="sendNotifyContext"
> xmlns="http://camel.apache.org/schema/spring";
> errorHandlerRef="errorHandler">
> <route id="sendToNotify">
> <from uri="..." />
> ....
> *<to uri="vm:myNotify" />*
> </route>
> </camelContext>
> <camelContext id="receiveNotifyContext"
> xmlns="http://camel.apache.org/schema/spring";
> errorHandlerRef="errorHandler">
> <route id="receiveNotify">
> *<from uri="vm:myNotify?size=2500" />*
> ....
> <to uri="..." />
> </route>
> </camelContext>
> The producer appears to send to vm:myNotify while the consumer is listening
> to a separate endpoint named vm:myNotify?size=2500, so the messages build up
> and are never received.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
