to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of-order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support ./artemis user add --user-command-user so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

to use FQQN syntax for both security-settings and JNDI lookup Support pausing dispatch during group rebalance (to avoid potential out-of- order consumption) Socks5h support 2.14.0 Full release notes so messaging operations can be performed as part of a JTA transaction. ClientSession instances group ClientConsumer instances and ClientProducer instances. ClientSession instances can be registered supported which should use a host:port combination that matches the group-address and group-port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has

supported which should use a host:port combination that matches the group-address and group- port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has with multiple network interfaces on the same machine, you may want to specify that the discovery group listens only only a specific interface. To do this you can specify the interface address with this specified in conjunction with localAddress . refreshTimeout - This is the period the discovery group waits after receiving the last broadcast from a particular server before removing that servers connector

supported which should use a host:port combination that matches the group-address and group- port from the corresponding broadcast-group configured on the ActiveMQ Artemis server(s). Each scheme has with multiple network interfaces on the same machine, you may want to specify that the discovery group listens only only a specific interface. To do this you can specify the interface address with this specified in conjunction with localAddress . refreshTimeout - This is the period the discovery group waits after receiving the last broadcast from a particular server before removing that servers connector