[
https://issues.apache.org/jira/browse/ARTEMIS-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Roskvist updated ARTEMIS-3771:
------------------------------------
Description:
Rework destination handling for the OpenWire-protocol
Mainly improves things for brokers with many destinations and for handling
clients not reusing JMS resources, but should be a nice overall improvement for
OpenWire.
Changes are:
openWireDestinationCache now global, also taking over the role for the
connection destination cache
Avoid calling BindingQuery since that method is expensive when dealing with a
large number of destinations
openwireDestinationCacheSize no longer has to be a power of 2
was:
Rework destination handling for the OpenWire-protocol
Mainly improves things for brokers with many destinations and for handling
clients not reusing JMS resources, but should be a nice overall improvement for
OpenWire.
Changes include:
openWireDestinationCache now global, also taking over the role for the
connection destination cache
Avoid calling BindingQuery since that method is expensive when dealing with a
large number of destinations
> Rework destination handling for the OpenWire-protocol
> -----------------------------------------------------
>
> Key: ARTEMIS-3771
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3771
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Major
>
> Rework destination handling for the OpenWire-protocol
>
> Mainly improves things for brokers with many destinations and for handling
> clients not reusing JMS resources, but should be a nice overall improvement
> for OpenWire.
> Changes are:
> openWireDestinationCache now global, also taking over the role for the
> connection destination cache
> Avoid calling BindingQuery since that method is expensive when dealing with a
> large number of destinations
> openwireDestinationCacheSize no longer has to be a power of 2
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
