Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.22.0
-
None
-
None
-
None
-
- Windows 10
- Apache Artemis 2.22.0 runs as service
- Broker is default
Description
There is an issue: ARTEMIS-856 about advanced destination options:
- timeBeforeDispatchStarts
- consumersBeforeDispatchStarts
It's closed as 'fixed' in 2.7.0 and we can see it in release notes.
These options are crucial when a queue uses Message Groups (JMSXGroupID)
There is no documentation about how to configure the ARTEMIS-856 fix.
When I try to configure a broker in a logical and generic way - I get the error:
2022-06-08 16:15:32,884 ERROR [org.apache.activemq.artemis.core.client] AMQ214019: Invalid configuration: org.xml.sax.SAXParseException; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:activemq:core":timeBeforeDispatchStarts}'. One of '{"urn:activemq:core":dead-letter-address, "urn:activemq:core":auto-create-dead-letter-resources, "urn:activemq:core":dead-letter-queue-prefix, "urn:activemq:core":dead-letter-queue-suffix, "urn:activemq:core":expiry-address, "urn:activemq:core":auto-create-expiry-resources, "urn:activemq:core":expiry-queue-prefix, "urn:activemq:core":expiry-queue-suffix, "urn:activemq:core":expiry-delay, "urn:activemq:core":min-expiry-delay, "urn:activemq:core":max-expiry-delay, "urn:activemq:core":redelivery-delay, "urn:activemq:core":redelivery-delay-multiplier, "urn:activemq:core":redelivery-collision-avoidance-factor, "urn:activemq:core":max-redelivery-delay, "urn:activemq:core":max-delivery-attempts, "urn:activemq:core":max-size-bytes, "urn:activemq:core":max-size-messages, "urn:activemq:core":max-size-bytes-reject-threshold, "urn:activemq:core":page-size-bytes, "urn:activemq:core":page-max-cache-size, "urn:activemq:core":address-full-policy, "urn:activemq:core":message-counter-history-day-limit, "urn:activemq:core":last-value-queue, "urn:activemq:core":default-last-value-queue, "urn:activemq:core":default-last-value-key, "urn:activemq:core":default-non-destructive, "urn:activemq:core":default-exclusive-queue, "urn:activemq:core":default-group-rebalance, "urn:activemq:core":default-group-rebalance-pause-dispatch, "urn:activemq:core":default-group-buckets, "urn:activemq:core":default-group-first-key, "urn:activemq:core":default-consumers-before-dispatch, "urn:activemq:core":default-delay-before-dispatch, "urn:activemq:core":redistribution-delay, "urn:activemq:core":send-to-dla-on-no-route, "urn:activemq:core":slow-consumer-threshold, "urn:activemq:core":slow-consumer-threshold-measurement-unit, "urn:activemq:core":slow-consumer-policy, "urn:activemq:core":slow-consumer-check-period, "urn:activemq:core":auto-create-jms-queues, "urn:activemq:core":auto-delete-jms-queues, "urn:activemq:core":auto-create-jms-topics, "urn:activemq:core":auto-delete-jms-topics, "urn:activemq:core":auto-create-queues, "urn:activemq:core":auto-delete-queues, "urn:activemq:core":auto-delete-created-queues, "urn:activemq:core":auto-delete-queues-delay, "urn:activemq:core":auto-delete-queues-message-count, "urn:activemq:core":config-delete-queues, "urn:activemq:core":auto-create-addresses, "urn:activemq:core":auto-delete-addresses, "urn:activemq:core":auto-delete-addresses-delay, "urn:activemq:core":config-delete-addresses, "urn:activemq:core":config-delete-diverts, "urn:activemq:core":management-browse-page-size, "urn:activemq:core":management-message-attribute-size-limit, "urn:activemq:core":default-purge-on-no-consumers, "urn:activemq:core":default-max-consumers, "urn:activemq:core":default-queue-routing-type, "urn:activemq:core":default-address-routing-type, "urn:activemq:core":default-consumer-window-size, "urn:activemq:core":default-ring-size, "urn:activemq:core":retroactive-message-count, "urn:activemq:core":enable-metrics, "urn:activemq:core":enable-ingress-timestamp}' is expected.
or
2022-06-08 17:12:41,447 ERROR [org.apache.activemq.artemis.core.client] AMQ214019: Invalid configuration: org.xml.sax.SAXParseException; cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:activemq:core":time-before-dispatch-starts}' ...
I've tried both ways without success:
Address: (preferred because of wildcards)
<address-settings> <address-setting match="*.something"> <timeBeforeDispatchStarts>5000</timeBeforeDispatchStarts> <consumersBeforeDispatchStarts>50</consumersBeforeDispatchStarts> </address-setting> </address-settings>
or
<address-settings> <address-setting match="*.something"> <time-before-dispatch-starts>5000</time-before-dispatch-starts> <consumers-before-dispatch-starts>50</consumers-before-dispatch-starts> </address-setting> </address-settings>
Queue:
<queues> <queue name="test.queue"> <address>test.queue</address> <durable>true</durable> <timeBeforeDispatchStarts>5000</timeBeforeDispatchStarts> <consumersBeforeDispatchStarts>50</consumersBeforeDispatchStarts> </queue> </queues>
Attachments
Issue Links
- is part of
-
ARTEMIS-856 Support advanced destination options
- Closed