[
https://issues.apache.org/jira/browse/CAMEL-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573100#comment-16573100
]
ASF GitHub Bot commented on CAMEL-12638:
----------------------------------------
davsclaus closed pull request #2459: CAMEL-12638: FluentProducerTemplate
should be thread-safe
URL: https://github.com/apache/camel/pull/2459
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> DefaultFluentProducerTemplate is not thread safe
> ------------------------------------------------
>
> Key: CAMEL-12638
> URL: https://issues.apache.org/jira/browse/CAMEL-12638
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.20.2
> Reporter: Lukasz
> Priority: Major
> Fix For: 2.21.3, 2.22.1, 2.23.0
>
> Attachments: image-2018-07-12-17-58-09-225.png
>
>
> I think we have rediscovered the CAMEL-10820 bug. A body of one request gets
> replaced with a body of proceeding request, in our case we use *request()*
> method instead of *asyncSend()*.
> We use camel together with spring-boot. Consider following code:
>
> {code:java}
> @Service
> public class UseCamelService {
> private FluentProducerTemplate producer;
> @Autowired
> public UseCamelService(FluentProducerTemplate producer) {
> this.producer = producer;
> }
> public String getValueFromCamel(String body) {
> return producer.to("route").withBody(body).request(String.class);
> }
> }
> {code}
> If *UseCamelService.getValueFromCamel()* gets called from two different
> threads it is possible for the latter one to override the body of the first
> one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
