Chapter 4. Known Issues

ENTMQBR-17 - AMQ222117: unable to start cluster connection
A broker cluster may fail to initialize properly in environments that support IPv6. The failure is due to a SocketException that is indicated by the log message Can’t assign requested address. To work around this issue, set the java.net.preferIPv4Stack system property to true.

ENTMQBR-463 - Attributes in clustering settings has order restrictions, would be nice to either have better error message or simply ignore the order
Currently the sequence of the elements in the cluster connection configuration has to be in a specific order. The workaround is to adhere to the order in the configuration schema.

ENTMQBR-520 - Receiving from address named same as queue bound to other address should not be allowed
A queue with the same name as an address must only be assigned to address. Creating a queue with the same name as an existing address, but bound to an address with a different name, is an invalid configuration. Doing so can result in incorrect messages being routed to the queue.

ENTMQBR-569 - Conversion of IDs from OpenWire to AMQP results in sending IDs as binary
When communicating cross-protocol from an A-MQ 6 OpenWire client to an AMQP client, additional information is encoded in the application message properties. This is benign information used internally by the broker and can be ignored.

ENTMQBR-599 - Define truststore and keystore by artemis cli
Creating a broker instance by using the --ssl-key, --ssl-key-password, --ssl-trust, and --ssl-trust-password parameters does not work. To work around this issue, set the corresponding properties manually in bootstrap.xml after creating the broker.

ENTMQBR-617 - Cert based authentication doesn’t work with AMQP and OpenWire clients
Authentication based on SSL certificates is not supported for AMQP and OpenWire clients.

ENTMQBR-636 - Journal breaks, causing JavaNullPointerException, under perf load (mpt)
To prevent IO-related issues from occurring when the broker is managing heavy loads, verify that the JVM is allocated with enough memory and heap space. See the section titled "Tuning the VM" in the Performance Tuning chapter of the ActiveMQ Artemis documentation.

ENTMQBR-648 - JMS Openwire client is unable to send messages to queue with defined 'purgeOnNoConsumer' or queue 'filter'
Using an A-MQ 6 JMS client to send messages to an address that has a queue with purgeOnNoConsumer set to true fails if the queue has no consumers. It is recommended that you do not set the purgeOnNoConsumer option when using A-MQ 6 JMS clients.

ENTMQBR-652 - List of known amq-jon-plugin bugs
This version of amq-jon-plugin has known issues with the MBeans for broker and queue.
Issues with the broker MBean:
- Closing a connection throws java.net.SocketTimeoutException exception
- listSessions() throws java.lang.ClassCastException
- Adding address settings throws java.lang.IllegalArgumentException
- getConnectorServices() operation cannot be found
- listConsumersAsJSON() operation cannot be found
- getDivertNames() operation cannot be found
- Listing network topology throws IllegalArgumentException
- Remove address settings has wrong parameter name
Issues with the queue MBean:
- expireMessage() throws argument type mismatch exception
- listDeliveringMessages() throws IllegalArgumentException
- listMessages() throws java.lang.Exception
- moveMessages() throws IllegalArgumentException with error message argument type mismatch
- removeMessage() throws IllegalArgumentException with error message argument type mismatch
- removeMessages() throws exception with error Can’t find operation removeMessage with 2 arguments
- retryMessage() throws argument type mismatch IllegalArgumentException

ENTMQBR-655 - [AMQP] Unable to send message when populate-validated-user is enabled
The configuration option populate-validated-user is not supported for messages produced using the AMQP protocol.

ENTMQBR-742 - JMS Queues are not being auto-deleted for Openwire and AMQP clients
Addresses and queues with <auto-delete-addresses> and <auto-delete-queues> set to true are not deleted when AMQ OpenWire JMS clients disconnect from them.

ENTMQBR-781 - [Error Codes] same Error Code(s) defined in different places with different reasons
Logging error codes are not unique for all broker log messages. Use the logger name, org.apache.activemq.artemis.core.server for example, to identify uniqueness.

ENTMQBR-897 - Openwire client/protocol issues with special characters in destination name
Currently AMQ OpenWire JMS clients cannot access queues and addresses that include the following characters in their name: comma (','), hash ('#'), greater than ('>'), and whitespace.

ENTMQBR-927 - broker.xml does not validate against artemis-configuration.xsd
The broker.xml configuration file does not validate against its XML schema.

ENTMQBR-940 - NPE thrown by QuorumVoteMessage.decode()
If a broker that is not configured with an <ha-policy> is added to a cluster that is using <replication> for its policy, the broker is not included during quorum votes taken after a failure within the cluster. Instead, an exception is thrown that the broker is missing an <ha-policy>. It is recommended that you configure all brokers in a cluster to use the same <ha-policy>.

ENTMQBR-943 - [AMQ7, Openwire, Compression] consuming openwire compressed bytemessage throws java.util.zip.DataFormatException: incorrect header check
When using the OpenWire protocol to send small, compressed ByteMessages that have JMS properties set for a Queue, an exception is thrown on the consumer side when it tries to decompress the message. See the Knowledge Base article on the Red Hat Customer Portal for more details: https://access.redhat.com/solutions/3269061.

ENTMQBR-944 - [A-MQ7, Hawtio, RBAC] User gets no feedback if operation access was denied by RBAC
The console can indicate that an operation attempted by an unauthorized user was successful when it was not.

ENTMQBR-945 - Non-persistent messages lost in non-failure scenarios when authorization fails, because delivery mode defaults to asynchronous
Clients may not notice the loss of non-persistent messages. Message loss is often associated with an obvious failure, such as the broker stopping or the storage provider disconnecting. However, the asynchronous behavior of the default delivery mode can lead to the loss of non-persistent messages in other situations too, such as failing authorization or trying to use a queue that is not configured.

ENTMQBR-956 - [AMQ7, AMQP, JMX, DeliveringCount] JMX operation "listDeliveringMessages()” returns empty string when deliveringCount > 0
The JMX operation listDeliveringMessages() does not return messages that were consumed in a transaction by an AMQ JMS client.