Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/2035
Couple of points & questions:
* This PR is putting JMS-specific logic into the core broker where it
doesn't belong.
* Is the `clientID` being returned here supposed to be the JMS client ID?
The client ID on the connection object being retrieved is not the JMS client
ID. The JMS client ID is set on the core session's internal meta-data.
* The JMS prefixes that are being used here to determine the are no longer
valid as they were removed in 2.0.
* The test is only validating that the fields exist in the reply and not
that they actually have accurate values.
* Is the new `durable` flag meant to be some kind of indication about a JMS
durable subscriber? The value for `durable` being returned is for the queue to
which the consumer is attached which isn't directly related to JMS durable
subscriptions.
---
