This slipped off my radar, but I just had a quick look at your code. The JNDI stuff looks like a mish-mash of Wildfly and Artemis implementation properties. One important thing to keep in mind here is that the JNDI implementations between Artemis and Wildfly are completely different and each requires their own unique property values to be configured appropriately. If you're connecting to Wildfly you have to use the appropriate properties for their JNDI implementation, and if you're connecting to Artemis you have to use the appropriate properties for our implementation. Another thing to keep in mind is the the Wildfly JNDI is a client/server implementation meaning the JNDI client implementation actually goes over the network and performs the lookup on the remote server. The Artemis JNDI implementation is 100% client-side meaning that the JNDI client simply instantiates the JMS admin objects (connection factories, destinations, etc.) without doing any kind of remote lookup. It is up to the user to configure the Artemis JNDI properties appropriately so that it contains the resource JMS admin objects.
I guess my first question about your code would be - are you trying to use Wildfly or Artemis JNDI? Justin On Fri, Aug 10, 2018 at 4:06 PM, JGlass <jason.gl...@cableone.biz> wrote: > Done banging my head on this and trying all sorts of different things - > opening a Red Hat Support ticket ;-( If they provide a working example > I'll > post it here if I'm allowed! > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
