There is no limit on the destination cache for a core JMS client. For a long-lived connection sending to lots of different destinations (e.g. in a request-reply use-case involving temporary queues) this can present a significant problem.
- clones
-
JBEAP-18316 [GSS](7.3.z) ENTMQBR-2759 - ARTEMIS-2451 - Eliminate knownDestinations cache
-
- Closed
-
- is blocked by
-
-
- Closed
-
-
-
- Closed
-
- is incorporated by
-
JBEAP-17386 [GSS](7.2.z) Upgrade Artemis from 2.9.0.redhat-00005 to 2.9.0.redhat-00009
-
- Closed
-
