> Any chance the WF10-problem could also be a configuration error on my end?
I think so. > So my question is basically: do you see the same NPE when connecting to WF-10.1.0 No. I don't see the NPE when using Wildfly 10.1.0.Final. I used the same config as before, but included the Netty MQTT codec JAR since the version of Netty shipped with Wildfly 10.1.0.Final doesn't include it by default. It works from MQTTBox using the "mqtt / tcp" protocol, but not the "ws" protocol. I'm not sure what the issue there is, but I assume it's related to a problem with the MQTT implementation in Artemis 1.1. It works fine with both protocols in Artemis 1.5.5 in Wildfly 11.0.0.CR1. Justin On Tue, Sep 26, 2017 at 1:38 PM, thoutekier <thomas.houtek...@barco.com> wrote: > Justin, > > If I use your configuration on WF-11, I don't have the errors anymore. So I > probably messed up there. However, I don't succeed in connecting with > MQTT-box (connection-error). Connecting to the standalone-artemis works > without any issue. I assume this will be a problem on my end, I haven't > figured it out yet. > > Any chance the WF10-problem could also be a configuration error on my end? > I > didn't find any official documentation, so maybe I did something wrong in > my > configuration-improvisation. > So my question is basically: do you see the same NPE when connecting to > WF-10.1.0 > I'll see if I can get the artemis-integrationtests up and running, thanks > for pointing me to those. > > Thanks a lot! > Thomas > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
