Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
The Message.getMessageId() method are not much in use, only for logging purposes (we use exchange id as uuid in Camel).
But we generate a new id for the message which takes up resources. We should instead let message id be part of the component protocol it comes from, eg JMSMessageID. And the only component that does this are in fact JMS via the createMessageId() method.
Attachments
Issue Links
- relates to
-
CAMEL-14354 camel-core - Optimize unnecessary object allocations
- Resolved