From 16526433e1446223871ff02ad8da0b62825ff885 Mon Sep 17 00:00:00 2001 From: Clebert Suconic Date: Fri, 5 Apr 2019 16:19:38 -0400 Subject: [PATCH] NO-JIRA updating duplicated XSD on tools --- .../test/resources/artemis-configuration.xsd | 699 ++++++++++++++---- 1 file changed, 561 insertions(+), 138 deletions(-) diff --git a/artemis-tools/src/test/resources/artemis-configuration.xsd b/artemis-tools/src/test/resources/artemis-configuration.xsd index 5a5d4f3bfa..ebafee2017 100644 --- a/artemis-tools/src/test/resources/artemis-configuration.xsd +++ b/artemis-tools/src/test/resources/artemis-configuration.xsd @@ -22,6 +22,8 @@ elementFormDefault="qualified" version="1.0"> + + @@ -34,6 +36,14 @@ + + + + This defines the prefix which we will use to parse System properties for the configuration. Default= + + + + @@ -44,14 +54,23 @@ + + + + This enables making AMQP subscription queue names, match core queue names, for better interoperability between protocols. + Note: Enabling this to an existing broker if pre-existing amqp durable subscriptions already existed will require + clients to re-subscribe and to clean up old subscription names. + + + + If true then the ActiveMQ Artemis Server will make use of any Protocol Managers that are in available - on the - classpath. If false then only the core protocol will be available, unless in Embedded mode where users - can inject their own Protocol Managers. + on the classpath. If false then only the core protocol will be available, unless in Embedded mode + where users can inject their own Protocol Managers. @@ -196,7 +215,7 @@ - XXX + DEPRECATED: the name of the factory class to use for log delegation @@ -317,6 +336,14 @@ + + + + how often (in ms) to scan for addresses and queues that need to be deleted + + + + @@ -336,7 +363,7 @@ - a list of <class-name/> elements with the names of classes to use for interceptor incoming + a list of <class-name/> elements with the names of classes to use for intercepting incoming remoting packets @@ -345,7 +372,7 @@ - a list of <class-name/> elements with the names of classes to use for interceptor outcoming + a list of <class-name/> elements with the names of classes to use for intercepting outgoing remoting packets @@ -637,10 +664,11 @@ - + - The size of the internal buffer on the journal in KiB. + The size (in bytes) of the internal buffer on the journal. Supports byte notation like "K", "Mb", + "GB", etc. @@ -671,10 +699,10 @@ - + - the size (in bytes) of each journal file + The size (in bytes) of each journal file. Supports byte notation like "K", "Mb", "GB", etc. @@ -720,6 +748,14 @@ + + + + the length of time in seconds to wait when opening a new Journal file before timing out and failing + + + + @@ -728,11 +764,11 @@ - + - Global Max Size before all addresses will enter into their Full Policy configured upon messages being - produced. + Size (in bytes) before all addresses will enter into their Full Policy configured upon messages being + produced. Supports byte notation like "K", "Mb", "GB", etc. @@ -740,7 +776,7 @@ - Max percentage of disk usage before the system blocks or fail clients. + Max percentage of disk usage before the system blocks or fails clients. @@ -786,91 +822,191 @@ + + + + should analyze response time on critical paths and decide for broker log, shutdown or halt. + + + + + + + + The default timeout used on analyzing timeouts on the critical path. + + + + + + + + The timeout here will be defaulted to half critical-analyzer-timeout, calculation happening at runtime + + + + + + + + Should the server log, be shutdown or halted upon critical analysis failure. + + + + + + + + + + + a list of security settings + - - - - - - a permission to add to the matched addresses - - - - - - - - - the type of permission - - - - - - - a comma-separated list of roles to apply the permission to - - - - - - - - + + + + - regular expression for matching security roles against addresses + a permission to add to the matched addresses + + + + + + + + + the type of permission + + + + + + + a comma-separated list of roles to apply the permission to + + + + + + + + + + + pattern for matching security roles against addresses; can use wildards + + + + + + + + + + + a plugin + + + + + + + + + the name of the setting + + + + + + + the value for the setting + + + + + + + + + + + the name of the plugin class to instantiate + + + + + + + + + + + + + the name of the external role + + + + + + + the comma delimited name of the internal role(s) - + + + + + + + + + a list of broker-plugins + + + + + - a plugin + a broker plugin - - - - - - the name of the setting - - - - - - - the value for the setting - - - - - + + + + properties to configure a plugin + + - the name of the plugin class to instantiate + the name of the broker plugin class to instantiate - + @@ -913,12 +1049,68 @@ - + + + + + + A comma separated list of IPs to be used to validate if the broker should be kept up + + + + + + + + A comma separated list of URLs to be used to validate if the broker should be kept up + + + + + + + + A frequency in milliseconds to how often we should check if the network is still up + + + + + + + + A timeout used in milliseconds to be used on the ping. + + + + + + + + The network interface card name to be used to validate the address. + + + + + + + + The ping command used to ping IPV4 addresses. + + + + + + + + The ping command used to ping IPV6 addresses. + + + - Wildcard addresses format + parameters to configure wildcard address matching format @@ -946,9 +1138,20 @@ - - - + + + + a local address to which the datagram socket is bound + + + + + + + a local port to which the datagram socket is bound + + + @@ -999,7 +1202,6 @@ - @@ -1007,7 +1209,6 @@ - @@ -1158,11 +1359,11 @@ - + - Any message larger than this size is considered a large message (to be sent in - chunks) + Any message larger than this size (in bytes) is considered a large message (to be sent in + chunks). Supports byte notation like "K", "Mb", "GB", etc. @@ -1241,18 +1442,19 @@ - + - Once the bridge has received this many bytes, it sends a confirmation + Once the bridge has received this many bytes, it sends a confirmation. Supports byte notation like + "K", "Mb", "GB", etc. - + - Producer flow control + Producer flow control. Supports byte notation like "K", "Mb", "GB", etc. @@ -1282,6 +1484,14 @@ + + + + how should the routing-type on the bridged messages be set? + + + + @@ -1317,6 +1527,8 @@ + + @@ -1425,6 +1637,7 @@ + @@ -1450,32 +1663,30 @@ - - - - - - - - - - - - - - - - - - - - + + + + + optional name of transformer class + + + + + + + properties to configure the transformer class + + + + + + @@ -1586,10 +1797,11 @@ - + - Messages larger than this are considered large-messages + Messages larger than this are considered large-messages. Supports byte notation like + "K", "Mb", "GB", etc. @@ -1654,8 +1866,7 @@ DEPRECATED: use message-load-balancing-type instead. Select STRICT to mimic - forward-when-no-consumers=true - and ON_DEMAND to mimic forward-when-no-consumers=false. + forward-when-no-consumers=true and ON_DEMAND to mimic forward-when-no-consumers=false. @@ -1683,18 +1894,19 @@ - + - The size (in bytes) of the window used for confirming data from the server connected to. + The size (in bytes) of the window used for confirming data from the server connected to. Supports + byte notation like "K", "Mb", "GB", etc. - + - Producer flow control + Producer flow control. Supports byte notation like "K", "Mb", "GB", etc. @@ -1753,7 +1965,7 @@ - XXX -- this is a duplicate... + name of discovery group used by this cluster-connection @@ -1851,20 +2063,12 @@ - + how should the routing-type on the diverted messages be set? - - - - - - - - @@ -1939,6 +2143,20 @@ + + + + The table name used to large message files + + + + + + + The table name used to hold shared store data + + + @@ -1946,6 +2164,27 @@ + + + + The period in milliseconds of the keep alive service of a JDBC lock. + + + + + + + The time in milliseconds a JDBC lock is considered valid without keeping it alive. + + + + + + + The JDBC jouranl sync period in milliseconds. + + + @@ -2206,6 +2445,50 @@ + + + + Whether or not this live broker should vote to remain as live if replication is lost. + + + + + + + The quorum size used for voting after replication loss, -1 means use the current cluster size + + + + + + + + If we start as a replica and lose connection to the master, how many times should we attempt to vote + for quorum before restarting + + + + + + + How long to wait (in milliseconds) between each vote + + + + + + + How long to wait (in seconds) for vote results + + + + + + + If we start as a replica how long to wait (in milliseconds) before trying to replicate again after failing to find a replica + + + @@ -2279,6 +2562,50 @@ + + + + If we have to start as a replicated server decide whether or not this live broker should vote to remain + as live if replication is lost. + + + + + + + If we have to start as a replicated server or we are a backup and lose connection to live, the quorum size + used for voting after replication loss, -1 means use the current cluster size + + + + + + + If we lose connection to the master, how many times should we attempt to vote for quorum before restarting + + + + + + + How long to wait (in milliseconds) between each vote + + + + + + + How long to wait (in milliseconds) before trying to replicate again after failing to find a replica + + + + + + + How long to wait (in seconds) for vote results + + + @@ -2343,6 +2670,13 @@ + + + + Will the master startup wait until it is activated + + + @@ -2497,7 +2831,7 @@ - + A reference to a cluster connection address @@ -2603,11 +2937,11 @@ - + the maximum size (in bytes) for an address (-1 means no limits). This is used in PAGING, BLOCK and - FAIL policies. + FAIL policies. Supports byte notation like "K", "Mb", "GB", etc. @@ -2623,10 +2957,11 @@ - + - the page size (in bytes) to use for an address + The page size (in bytes) to use for an address. Supports byte notation like "K", "Mb", + "GB", etc. @@ -2691,7 +3026,7 @@ - whether the queue should be non-destructive by default + whether the queue should be non-destructive by default @@ -2731,7 +3066,8 @@ - the default delay to wait before dispatching if number of consumers before dispatch is not met for queues under the address. + the default delay (in milliseconds) to wait before dispatching if number of consumers before + dispatch is not met for queues under the address. @@ -2780,7 +3116,7 @@ - How often to check for slow consumers on a particular queue. Measured in minutes. + How often to check for slow consumers on a particular queue. Measured in seconds. @@ -2836,6 +3172,30 @@ + + + + whether or not to delete created queues when the queue has 0 consumers and 0 messages + + + + + + + + how long to wait (in milliseconds) before deleting auto-created queues after the queue has 0 + consumers. + + + + + + + + the message count the queue must be at or below before it can be evaluated to be auto deleted, 0 waits until empty queue (default) and -1 disables this check. + + + @@ -2857,7 +3217,6 @@ whether or not to automatically create addresses when a client sends a message to or attempts to consume a message from a queue mapped to an address that doesn't exist - a queue @@ -2870,12 +3229,21 @@ + + + + how long to wait (in milliseconds) before deleting auto-created addresses after they no longer + have any queues + + + + What to do when an address is no longer in broker.xml. OFF = will do nothing addresses will remain, - FORCE = delete queues, and address even if messages remaining. + FORCE = delete address and its queues even if messages remaining. @@ -2886,8 +3254,7 @@ - + how many message a management resource can browse @@ -2895,12 +3262,53 @@ + + + + purge the contents of the queue once there are no consumers + + + + + + + + the maximum number of consumers allowed on this queue at any one time + + + + + + + + the routing-type used on auto-created queues + + + + + + + + the routing-type used on auto-created addresses + + + + + + + + the default window size for a consumer + + + + - XXX + pattern for matching settings against addresses; can use wildards @@ -2919,7 +3327,7 @@ - how many connections are allowed by the matched entity (-1 means no limit, default is -1) + how many connections are allowed by the matched user (-1 means no limit, default is -1) @@ -2927,7 +3335,7 @@ - how many queues can be created by the matched entity (-1 means no limit, default is -1) + how many queues can be created by the matched user (-1 means no limit, default is -1) @@ -2992,10 +3400,24 @@ - - + + + + + + + + + + + + + + + + @@ -3048,7 +3470,7 @@ - The address name to matches incoming message addresses + The address name to match incoming message addresses @@ -3072,7 +3494,7 @@ - deprecated please use routing-enabled. + deprecated please use routing-enabled. @@ -3107,4 +3529,5 @@ +