]
Justin Bertram commented on WFLY-9372:
--------------------------------------
When I tested with Wildfly 11.0.0.CR1 I didn't see any issue. Clients were able to
subscribe, publish, etc. as expected. Here's my module.xml:
{code:xml}
<module xmlns="urn:jboss:module:1.5"
name="org.apache.activemq.artemis.protocol.mqtt">
<resources>
<resource-root path="artemis-mqtt-protocol-1.5.5.jbossorg-007.jar"
/>
</resources>
<dependencies>
<module name="io.netty"/>
<!-- required to load ActiveMQ protocol SPI -->
<module name="org.apache.activemq.artemis"/>
<module name="org.jboss.logging"/>
</dependencies>
</module>
{code}
Note, this doesn't include netty-codec-mqtt-5.0.0.Alpha2.jar as those classes are
already included in the io.netty module which contains Netty 4.1.9.Final.
I added this to standalone-full.xml:
{code:xml}
<profile>
...
<subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">
...
<security enabled="false"/>
...
<remote-acceptor name="mqtt-acceptor"
socket-binding="mqtt">
<param name="protocols" value="MQTT"/>
</remote-acceptor>
...
</subsystem>
...
</profile>
...
<socket-binding-group name="standard-sockets"
default-interface="public"
port-offset="${jboss.socket.binding.port-offset:0}">
...
<socket-binding name="mqtt" port="1883"/>
</socket-binding-group>
{code}
NullpointerException in artemis-server-1.1.0.wildfly-017 (and
artemis-server-1.5.5.jbossorg-007.jar) when using MQTT
--------------------------------------------------------------------------------------------------------------------
Key: WFLY-9372
URL:
https://issues.jboss.org/browse/WFLY-9372
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.1.0.Final, 11.0.0.CR1
Environment: java8
Reporter: Thomas Houtekier
Assignee: Jeff Mesnil
Attachments: screenshot.png, server.log, standalone-full-ha.xml
When connecting a MQTT-client to a wildfly-10.1.0.Final (with embedded artemis 1.1.0),
the following NPE is thrown.
{code}
Sep:12,15:57:48,464 WARNING (:Thread-2 (activemq-netty-threads-345981593):)
[io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it
reached at the tail of the pipeline. It usually means the last handler in the pipeline did
not handle the exception.: io.netty.handler.codec.DecoderException:
java.lang.NullPointerException
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:391)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:311)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:218)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:204)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:828)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:625)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
Caused by: java.lang.NullPointerException
at
org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:171)
[artemis-server-1.1.0.wildfly-017.jar:]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:360)
[netty-all-4.0.33.Final.jar:4.0.33.Final]
... 9 more
{code}
for more info, see
https://developer.jboss.org/message/976007
Reproducing in straightforward, see 'steps to reproduce'.
I'm not sure if this is related to the integration of artemis into wildfly, or to the
artemis server itself.