The updated dropMessage method only decrements the destination metrics
if a message is removed from the pagedInMessages list to prevent
duplicate updates. There is also a case where we still need to update
metrics if the message never makes it into the pagedInMessages list in
the first place and that is on expiration so this patch fixes that. A
couple existing tests found this issue.
(cherry picked from commit 6e468b4540754cad5cd30de373cadc026c998669)
Only update metrics counters when message is removed from the
pagedInMessages list which is important to check in case of duplicates
(cherry picked from commit 021c82859cf4361eb31b21fdbac17655ae9e368d)
Need to remove the portion of the test that looks at the dispatched list
for TopicSubscription as that class no longer tracks message references
(cherry picked from commit 84126d8a7a7eb9faf44bef687dcf647e84173f22)
To save memory usage in some use cases add a new flag to PolicyEntry
called useTopicSubscriptionInflightStats to allow disabling the
inflight stats
(cherry picked from commit 65b0f2ad0d48845ad54681ac0eff832de122e2a9)
For the TopicSubscription case we can reduce the inflight statistics
memory footprint by not storing the entire message reference for in
flight messages and instead just a subset of the information needed.
(cherry picked from commit f69fd6f0020290752a7424479821c22d94f9b8b7)
StoreDurableSubscriberCursor now properly uses a timeout value when
attempting to add to the temporary store for non-persistent messages to
prevent an indefinite wait on free space
(cherry picked from commit 5e2adc0ed7dfe2e827bdef878f1c8cde12ff5773)
Update to latest Qpid JMS and Proton-J and the matching netty version
for Qpid JMS 4.1.22.Final
(cherry picked from commit 0bb4a5c3ab43b0f10f4a255f134de5b8533eb67d)
When multiple wildcard policies exist in a hierarchy it was possible for
the wrong policy to be selected when configuring a destination
(cherry picked from commit 2ce1c1352fb64ecf1d3018e2b0f7cabeba99b589)
This updates the AMQP libs Qpid JMS and Proton-J, also updates netty to
4.1.19.Final to match the version used for Qpid JMS
(cherry picked from commit a3f65e0aecfb1dbc8e78dbee336f2f74abdfe8bb)
This mostly fixes the url1/url2 copy and paste problem. It uses a bit more readable property syntax and introduces a single sentence (plain text) summary for class Javadoc and adds some links.
This updates the AMQP libs Qpid JMS and Proton-J, also updates netty to
4.1.18.Final to match the version used for Qpid JMS
(cherry picked from commit d3e439378405afb699fcbfc63d9342fbb6ad77ce)
Use the spec defined values when casting the Map from the
ApplicationProperties section.
(cherry picked from commit e7bce023de48591475781ba024104f8010a696fc)
The default behavior by the OpenWire client will be to send generic
platform details to the server with a new flag to send more specific
information.
(cherry picked from commit 5fa0bbd5156f29d97dcf48fd9fdb6a0488a8df1a)
We need to properly handle the re-addition of network proxy durables
after the brokers are restarted so removal is done properly
(cherry picked from commit 6013441a9a7c4a13f7412d6d72638de0f420e6a3)
The client id token that is used to separate parts of a generated local
client id in a network bridge should be configurable so bridge names and
broker names can contain underscores if desired
(cherry picked from commit 3ca439cadaa8c40f506aa1ef683b36624d216254)
Significantly reworking previous fix so that the client id is properly
changed when tracking network proxy subscriptions. This makes it so
removal is done properly
(cherry picked from commit 41211c78d19b545a2352584d3598346aa3705be4)
Durable network proxy subs will now be properly created across multiple
bridges when 3 or more brokers are used. Demand will be properly synced
and removed.
(cherry picked from commit 96ce14b278fef9e5f428f1c3c07ce5c09fd8f9a8)
