[
https://issues.apache.org/jira/browse/CAMEL-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120732#comment-13120732
]
Achim Nierbeck edited comment on CAMEL-4503 at 10/10/11 7:58 AM:
-----------------------------------------------------------------
Unfortunately I just realized that the mentioned workaround doesn't work :(
I'm investigating why it isn't I'm down to the following right now:
answer = endpoints.get(getEndpointKey(uri));
in DefaultCamelContext does give me the wrong Endpoint, at least it's bound to
the wrong URI.
it's called from
endpoint = resolveEndpoint(exchange, recipient);
in RecipientListProcessor.createProcessorExchangePairs(...)
The following scenario doesn't work right now for the workaround, this might be
a different bug though:
- Recipient A is resolved the way it should work and can be called
- if Recipient B is questioned it also works and can be used.
- if Recipient A is questioned from the cache again, Recipient B is provided
and therefore the requests end up
on the wrong host.
I also added a comment to the mailing-list about this.
was (Author: achim_nierbeck):
Unfortunately I just realized that the mentioned workaround doesn't work :(
I'm investigating why it isn't I'm down to the following right now:
answer = endpoints.get(getEndpointKey(uri));
in DefaultCamelContext does give me the wrong Endpoint, at least it's bound to
the wrong URI.
it's called from
endpoint = resolveEndpoint(exchange, recipient);
in RecipientListProcessor.createProcessorExchangePairs(...)
but maybe this is also because it seems to be a singleton, maybe setting it to
non-singleton
does work :)
> Recipient List cannot vary destination by changing property in an expression
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4503
> URL: https://issues.apache.org/jira/browse/CAMEL-4503
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.8.1
> Reporter: Jonathan Anstey
>
> This is probably due to producers being cached based on unresolved endpoint
> URI, rather than the resolved endpoint URI. Haven't tested this theory out
> though.
> See message on user list http://markmail.org/message/sdysp6sspq5lomf4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
