[
https://issues.apache.org/jira/browse/CAMEL-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267312#comment-14267312
]
Claus Ibsen commented on CAMEL-8204:
------------------------------------
I wonder if we should not fail instead of logging a warning? If the end user
provides a custom JMSCorrelationID that is already in use, then there is a
duplicate error, and we should not send the message.
Its just that today nobody normally experience this situation as the out of the
box generators makes unique ids. But if ppl use their own id generator they may
do this wrong. And IMHO its better for Camel to detect this and fail sending
the message which the end user can see asap.
> Write warning log if the JMS correlationId is not unique.
> ---------------------------------------------------------
>
> Key: CAMEL-8204
> URL: https://issues.apache.org/jira/browse/CAMEL-8204
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.13.4, 2.14.2, 2.15.0
>
>
> It could help us to find out the reason of the thread block issue that the
> JmsProducer sends the request/reply message when there is duplicated
> correlationId.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
