Re: wildfly-10.1.0.Final integration for MQTT not working

Thanks Justin, This is much appreciated. I'll have to rest if for a while now, other priorities. I'll pick this up later again. Thomas -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: wildfly-10.1.0.Final integration for MQTT not working

> 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 co

Re: wildfly-10.1.0.Final integration for MQTT not working

The Wildfly tests, and the wildfly dev team are focused on JEE (J2EE or whatever is names these days). The Wildfly team is not doing any testing on any other protocols or advanced messaging features available in other protocols. Artemis in wildfly is meant to provide wildfly with the requirement f

Re: wildfly-10.1.0.Final integration for MQTT not working

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

Re: wildfly-10.1.0.Final integration for MQTT not working

I also just tested with the MQTTBox Chrome plugin and it worked fine as well. Justin On Tue, Sep 26, 2017 at 11:28 AM, Justin Bertram wrote: > Here's my module.xml: > > > > /> > > > > > > > > > > > I added this to standalone-fu

Re: wildfly-10.1.0.Final integration for MQTT not working

Here's my module.xml: I added this to standalone-full.xml: ... ... ... ... ...

Re: wildfly-10.1.0.Final integration for MQTT not working

FWIW I just integrated MQTT with Wildfly 11.0.0.CR1 and ran org.apache.activemq.artemis.tests.integration.mqtt.imported.MQTTTest#testSendAndReceiveMQTT against it and everything worked. Justin On Tue, Sep 26, 2017 at 10:55 AM, Justin Bertram wrote: > The Artemis integration code for Wildfly i

Re: wildfly-10.1.0.Final integration for MQTT not working

The Artemis integration code for Wildfly is in the Wildfly project [1]. The problem you hit in Wildfly 11.0.0.CR1 looks odd to me. The class io.netty.handler.codec.mqtt.MqttEncoder from Netty 4.1.9.Final (which ships in Wildfly) does, in fact, contain the field "INSTANCE" so I'm not sure why you

Re: wildfly-10.1.0.Final integration for MQTT not working

* using artemis-1.1.0 standalone works out-of-the-box: it has by default support for MQTT in the config, and it works if I connect using an MQTT-client * using Wildfly-11.0.0.CR1: 2017-09-26 17:12:25,837 WARNING [io.netty.channel.DefaultChannelPipeline] (Thread-2 (activemq-netty-threads)) An excep

Re: wildfly-10.1.0.Final integration for MQTT not working

I think there's still value in you determining whether this use case works in standalone Artemis. If your existing code works as expected against standalone Artemis but not against Artemis embedded in Wildfly, you'll have demonstrated that the problem is within Wildfly, which might make it more lik

Re: wildfly-10.1.0.Final integration for MQTT not working

> Or, alternatively, don't use the internal artemis anymore, and only rely on the external. That is probably even more work. Assuming you're using managed resources (e.g. MDBs for consuming and pooled-connection-factory for sending) and don't have connection configuration details littered through

Re: wildfly-10.1.0.Final integration for MQTT not working

Hi Justin, I appreciate the suggestion, but I don't consider that an option. What I want to do is expose the queues and topic of the internal jms-bus over MQTT. JMS is used extensively in my application and I currently expose access to those messages outside of the server using a http-wrapper: a p

Re: wildfly-10.1.0.Final integration for MQTT not working

To be clear, I would expect it to work. There's no explicit reason MQTT shouldn't work in Artemis embedded in Wildfly. There's a bug somewhere preventing it from working. I'm just trying to give you options to work-around the issue given I don't have a lot of motivation to fix it since there is

Re: wildfly-10.1.0.Final integration for MQTT not working

yes, I understand. It certainly looks like that :-) But, since artemis has mqtt-support (according the documentation anyway, as I said I didn't try it myself), and since the protocols (stomp, amps, ...) in artemis are pluggable, it might just work in wildfly too. I must say that the wildfly docume

Re: wildfly-10.1.0.Final integration for MQTT not working

I guess my point is that you *don't* have one available in the Wildfly that you're using due to these issues you're running into (regardless of whether or not they are legitimate bugs). Wildfly embeds Artemis in order to fulfill the JMS implementation requirement of Java EE. Wildfly isn't trying

Re: wildfly-10.1.0.Final integration for MQTT not working

No, I haven't actually. It is not usefull for me. I don't want an 'out-of-process' MQTT broker, when I have one available in the wildfly that I'm using. Thomas -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: wildfly-10.1.0.Final integration for MQTT not working

Have you tried using standalone Artemis 2.3.0? Justin On Thu, Sep 21, 2017 at 2:01 PM, thoutekier wrote: > As suggested on the jboss-forum, I created an issue for this on both > wildfly > and artemis projects, with steps to reproduce the problem. > https://issues.apache.org/jira/browse/ARTEMIS

Re: wildfly-10.1.0.Final integration for MQTT not working

As suggested on the jboss-forum, I created an issue for this on both wildfly and artemis projects, with steps to reproduce the problem. https://issues.apache.org/jira/browse/ARTEMIS-1430 https://issues.jboss.org/browse/WFLY-9372 -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User

Re: wildfly-10.1.0.Final integration for MQTT not working

The plan/hope is that Artemis will become ActiveMQ 6.x succeeding ActiveMQ 5.x, but for right now they are sibling products within the overarching ActiveMQ project. On Sep 13, 2017 7:03 AM, "thomas.houtek...@barco.com" < thomas.houtek...@barco.com> wrote: > Thanks for the input! > Yes indeed, it

Re: wildfly-10.1.0.Final integration for MQTT not working

Martyn Taylor wrote > This is using a very old version of Artemis. I would recommend you bump > the Artemis dependency version to at least the latest version of 1.x > (currently 1.5.5). Hi Martyn, I just tried that: I upgraded the artemis-implementation in Wildfly-10 to 1.5.5 (I took the artemi

Re: wildfly-10.1.0.Final integration for MQTT not working

Thanks for the input! Yes indeed, it seems to be embedded artemis. It is not obvious to me what the difference is between ActiveMQ and ActiveMQ artemis. The names are sometimes interchanged, so it seems. It's possible that it is an old version. Probably 1.1.0. That is however not very clear if you

Re: wildfly-10.1.0.Final integration for MQTT not working

This is using a very old version of Artemis. I would recommend you bump the Artemis dependency version to at least the latest version of 1.x (currently 1.5.5). On Wed, Sep 13, 2017 at 1:40 PM, aragoubi wrote: > I got the same problem, I think it's not yet implemented. > https://developer.jboss

Re: wildfly-10.1.0.Final integration for MQTT not working

I got the same problem, I think it's not yet implemented. https://developer.jboss.org/message/974758#974758 -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: wildfly-10.1.0.Final integration for MQTT not working

It appears from your stack trace that this is embedded Artemis, not embedded ActiveMQ 5.x. Is that right? On Sep 13, 2017 4:36 AM, "thomas.houtek...@barco.com" < thomas.houtek...@barco.com> wrote: > Hi, > > I'm trying to get MQTT working on wildfly-10.1.0.Final. WF10 contains > activemq embedded