[
https://issues.apache.org/jira/browse/ARTEMIS-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Houtekier updated ARTEMIS-1430:
--------------------------------------
Description:
When connecting a mqtt-client to wildfly-10.1.0.Final (which has
artemis-1.1.0), I hit a nullpointerexception.
{code}
2017-09-21 15:58:26,244 WARNING [io.netty.channel.DefaultChannelPipeline]
(Thread-1 (activemq-netty-threads-1317507622)) 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)
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:244)
at
org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:118)
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
at
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at
org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:171)
at
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:360)
... 12 more
{code}
I filedd this issue in the wildfly-jira:
https://issues.jboss.org/browse/WFLY-9372
At the suggestion of the wildfly-forum I bring this to your attention too by
filing it here as well: It is not clear if the problem originates in artemis,
or in the integration of artemis in wildfly, or both.
see also
http://activemq.2283324.n4.nabble.com/wildfly-10-1-0-Final-integration-for-MQTT-not-working-td4730581.html
The stacktrace looks a lot like the issue reported in
https://issues.jboss.org/browse/ENTMQBR-728
The steps to reproduce are described in
https://issues.jboss.org/browse/WFLY-9372
was:
When connecting a mqtt-client to wildfly-10.1.0.Final (which has
artemis-1.1.0), I hit a nullpointerexception.
{code}
{code}
I filedd this issue in the wildfly-jira:
https://issues.jboss.org/browse/WFLY-9372
At the suggestion of the wildfly-forum I bring this to your attention too by
filing it here as well: It is not clear if the problem originates in artemis,
or in the integration of artemis in wildfly, or both.
see also
http://activemq.2283324.n4.nabble.com/wildfly-10-1-0-Final-integration-for-MQTT-not-working-td4730581.html
The steps to reproduce are described in
https://issues.jboss.org/browse/WFLY-9372
> wildfly-10.1.0.Final integration for MQTT not working
> -----------------------------------------------------
>
> Key: ARTEMIS-1430
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1430
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, MQTT
> Affects Versions: 1.1.0, 1.5.5
> Environment: java8, artemis-110 embedded in wildfly-10.1.0
> Reporter: Thomas Houtekier
>
> When connecting a mqtt-client to wildfly-10.1.0.Final (which has
> artemis-1.1.0), I hit a nullpointerexception.
> {code}
> 2017-09-21 15:58:26,244 WARNING [io.netty.channel.DefaultChannelPipeline]
> (Thread-1 (activemq-netty-threads-1317507622)) 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)
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:244)
> at
> org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.channelRead(ProtocolHandler.java:118)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:318)
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:304)
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846)
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
> at
> org.apache.activemq.artemis.core.protocol.ProtocolHandler$ProtocolDecoder.decode(ProtocolHandler.java:171)
> at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:360)
> ... 12 more
> {code}
> I filedd this issue in the wildfly-jira:
> https://issues.jboss.org/browse/WFLY-9372
> At the suggestion of the wildfly-forum I bring this to your attention too by
> filing it here as well: It is not clear if the problem originates in artemis,
> or in the integration of artemis in wildfly, or both.
> see also
> http://activemq.2283324.n4.nabble.com/wildfly-10-1-0-Final-integration-for-MQTT-not-working-td4730581.html
> The stacktrace looks a lot like the issue reported in
> https://issues.jboss.org/browse/ENTMQBR-728
> The steps to reproduce are described in
> https://issues.jboss.org/browse/WFLY-9372
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
