Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1695
<Copied from the JIRA since we apparently don't read those comments any
more>
This doesn't actually strike me as being a bug on the send as many JMS
provider will indeed send the message asynchronously and if any error is
reported on send fail it'd be done via the JMS ExceptionListener on the
Connection. It would be nice if the createProducer failed here if not
authorized to write to the target destination but if using an anonymous
producer than again this seems to operate as many other JMS clients would.
The standard practice here would be to use a transaction to create a sync
point (i.e. the commit) where the broker would report the operation as failed
if any of the sends inside that TX failed for some reason. Since the
NON_PERSISTENT delivery mode is 'at-most-once' you shouldn't expect the same
QoS behaviors on the client send (unless of course you can configure that which
appears you could via the block option).
---
