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