[jboss-jira] [JBoss JIRA] (WFLY-7036) Add MQTT protocol support for JMS

[Kabir Khan (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan updated WFLY-7036:
-----------------------------
    Fix Version/s:     (was: 10.x.x TBD)


Resetting the fix version as it is still open and 10.0.0.TBD was a long time ago. If it should be resolved, please do so (and close) against the relevant fix version

> Add MQTT protocol support for JMS
> ---------------------------------
>
>                 Key: WFLY-7036
>                 URL: https://issues.jboss.org/browse/WFLY-7036
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JMS
>    Affects Versions: 10.1.0.Final
>            Reporter: Juraj Veverka
>            Assignee: Jeff Mesnil
>
> It would be great if MQTT protocol is supported by JMS subsystem in WildFly AS. As of WildFly 10, ActiveMQ is used as JMS implementation in WildFly AS. ActiveMQ supports MQTT protocol, but if I try to add remote-acceptor in <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
>                 <remote-acceptor name="netty-acceptor-mqtt" socket-binding="messaging-mqtt">
>                     <param name="protocols" value="MQTT,CORE"/>
>                 </remote-acceptor>
> When WildFly is started, I can see following log statement:
> 22:55:48,487 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221020: Started Acceptor at 127.0.0.1:7998 for protocols [CORE,AMQP,HORNETQ,STOMP]
> which means that MQTT protocol is not supportred, instead CORE,AMQP,HORNETQ,STOMP are activated.
> MQTT is used by IoT devices, it would be nice if WildFly 10.2.0 AS has out-of-the-box support.  



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)