Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
It does a lookup of the consumer to handover the exchange on each process. We can optimize this to do this once and reuse same consumer.
And then if the consumer is stopped/removed then we need a event listener to tell the producer that the consumer is gone and it needs to clear the state.
This avoids the synchronized lookup on each process
Attachments
Issue Links
- relates to
-
CAMEL-15657 JDK biased locking to be removed in Java 17
- Resolved
- links to