In my opinion the greatest power and flexibility comes when running the
broker standalone. Then you can scale up if necessary (e.g. "horizontally"
via clustering or "vertically" via better hardware), configure high
availability, easily add support for other protocols, etc. without having
to deal wi
Hi Justin.
Let me a last question.
The idea of useing Wildfly as an application server comes from a personal
project I developed a couple of years ago. It was a JEE application software
for tracking vehicles. The comunication with tracking devices was based on
Web services. Now the trend in track
Thanks for the update.
I think everything you said is correct. The initial confusion may have been
caused by the way the messaging subsystem in Wildfly exposes the Artemis
configuration. It's really meant to be used only as a JMS server so the
messaging subsystem configuration is geared towards th
Hi Justin
Thank you for yours advise. It gave me the clue to solve the problem.
Setting the Wildfly log to debug provided usefull info.
After an in deep reading of Apache Artemis user manual, and having carried
out many tests and configurations on both, standalone and wildfly16
embedded, I have
Are you getting an exception or error message on the client which provides
any additional information about what the problem might be when the
subscription attempt fails? Is anything logged in the server's log file?
You shouldn't need to define that "mqtt-connector" or specify it in the
"RemoteCon
Good evening.
I have been trying to set up Wildfly16 with support to MQTT on JMS.
After a week trying to set the system I have to say I am not been able to
have the system fully working.
Then I moved to standalone Artemis to get the hang of working with this
software.
To my surprise my first a
