Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9E73C200D0E for ; Tue, 26 Sep 2017 18:53:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9CE471609D7; Tue, 26 Sep 2017 16:53:50 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BBA4D1609C4 for ; Tue, 26 Sep 2017 18:53:49 +0200 (CEST) Received: (qmail 79069 invoked by uid 500); 26 Sep 2017 16:53:48 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 79058 invoked by uid 99); 26 Sep 2017 16:53:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 16:53:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F119FC7687 for ; Tue, 26 Sep 2017 16:53:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.175 X-Spam-Level: ** X-Spam-Status: No, score=2.175 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, HTML_OBFUSCATE_10_20=1.162, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id dBZxQnoRujri for ; Tue, 26 Sep 2017 16:53:45 +0000 (UTC) Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id CE10F5FAF3 for ; Tue, 26 Sep 2017 16:53:44 +0000 (UTC) Received: by mail-oi0-f43.google.com with SMTP id b184so12861809oii.13 for ; Tue, 26 Sep 2017 09:53:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=g0n18oP2V2RoQB3cyaLwAL9qktAqp+OEPVgklCZJiMU=; b=DTirXIHnV2jVWMpOfJnN+3OhbMdeCH4jwV+D6+vAN1YP3NPNhWd+Jy3S1pEpE2Kb8h ci8UxHDvvZ6wn/NTfWxQ03h4FR6zWvwz5iTRsh/A0r5Sx6NTtlDJysR0rtB0a3bETs1t ZHcJ6v+dJf7Hb6NbzUNtK/KJG56a+TWQKXLcl/B5Y/9WOX0XBcyij7BNtXg+PmbDQeH1 sn54vUYukaqlBFXao3dMM2e1W+mI1gdAuRz9dqQVWSqbvPdoYmaol9a2bqumicb+o3dh god7w2SqfaUsemmY3fRqMBzFhqfGgh+YqxylWz0MdcK1UIom3n+MBBsdL5vvqeWZBW6y Ahrg== X-Gm-Message-State: AHPjjUjh20V+TRnSKj6hFFVqrOR93KmQIOvWC2MUTLkg9TMGhrBrf6Ec wjD1+Oe0CUz8QvOFeIdVKoiRdsjm0dPkfjdK3u0o7A== X-Google-Smtp-Source: AOwi7QBMLx1/6uuzbCD8ii3rPNlq69nLFTd+PCf4fP0dIEXnnjePNETFG0P9TG27RQJNSLvKhG9XAQ29FqlzkFIpZg8= X-Received: by 10.157.7.84 with SMTP id 78mr2771876ote.175.1506444823974; Tue, 26 Sep 2017 09:53:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.139.27 with HTTP; Tue, 26 Sep 2017 09:53:43 -0700 (PDT) In-Reply-To: References: <1505307810381-0.post@n4.nabble.com> <1506020465129-0.post@n4.nabble.com> <1506021061169-0.post@n4.nabble.com> <1506062732492-0.post@n4.nabble.com> <1506082673562-0.post@n4.nabble.com> <1506439063115-0.post@n4.nabble.com> From: Justin Bertram Date: Tue, 26 Sep 2017 11:53:43 -0500 Message-ID: Subject: Re: wildfly-10.1.0.Final integration for MQTT not working To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a113724b89b70fd055a1a84b5" archived-at: Tue, 26 Sep 2017 16:53:50 -0000 --001a113724b89b70fd055a1a84b5 Content-Type: text/plain; charset="UTF-8" I also just tested with the MQTTBox Chrome plugin and it worked fine as well. Justin On Tue, Sep 26, 2017 at 11:28 AM, Justin Bertram wrote: > Here's my module.xml: > > > > /> > > > > > > > > > > > I added this to standalone-full.xml: > > > ... > > ... > > ... > socket-binding="mqtt"> > > > ... > > ... > > ... > default-interface="public" port-offset="${jboss.socket. > binding.port-offset:0}"> > ... > > > > > Justin > > > On Tue, Sep 26, 2017 at 11:18 AM, Justin Bertram > wrote: > >> FWIW I just integrated MQTT with Wildfly 11.0.0.CR1 and >> ran org.apache.activemq.artemis.tests.integration.mqtt. >> imported.MQTTTest#testSendAndReceiveMQTT against it and everything >> worked. >> >> >> Justin >> >> On Tue, Sep 26, 2017 at 10:55 AM, Justin Bertram >> wrote: >> >>> The Artemis integration code for Wildfly is in the Wildfly project [1]. >>> >>> The problem you hit in Wildfly 11.0.0.CR1 looks odd to me. The >>> class io.netty.handler.codec.mqtt.MqttEncoder from Netty 4.1.9.Final >>> (which ships in Wildfly) does, in fact, contain the field "INSTANCE" so I'm >>> not sure why you would be getting this exception unless there was something >>> odd going on with the classloading or something. >>> >>> Also, the integration instructions in the WFLY-9372 JIRA say to copy >>> netty-codec-mqtt-5.0.0.Alpha2.jar into the org.apache.activemq.artemis.protocol.mqtt >>> module, but that shouldn't be necessary in Wildfly 11.0.0.CR1 as the >>> io.netty module already contains those classes. I also don't see why >>> the org.apache.activemq.artemis.protocol.mqtt module would need >>> dependencies on javax.jms.api, javax.api, or org.slf4j. >>> >>> >>> Justin >>> >>> [1] https://github.com/wildfly/wildfly (see the "messaging-activemq" >>> module) >>> >>> On Tue, Sep 26, 2017 at 10:17 AM, thoutekier >> > wrote: >>> >>>> * 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.DefaultChann >>>> elPipeline] >>>> (Thread-2 (activemq-netty-threads)) 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.NoSuchFieldError: >>>> INSTANCE >>>> at >>>> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteT >>>> oMessageDecoder.java:442) >>>> at >>>> io.netty.handler.codec.ByteToMessageDecoder.channelRead(Byte >>>> ToMessageDecoder.java:248) >>>> at >>>> org.apache.activemq.artemis.core.protocol.ProtocolHandler$Pr >>>> otocolDecoder.channelRead(ProtocolHandler.java:128) >>>> at >>>> io.netty.channel.AbstractChannelHandlerContext.invokeChannel >>>> Read(AbstractChannelHandlerContext.java:362) >>>> at >>>> io.netty.channel.AbstractChannelHandlerContext.invokeChannel >>>> Read(AbstractChannelHandlerContext.java:348) >>>> at >>>> io.netty.channel.AbstractChannelHandlerContext.fireChannelRe >>>> ad(AbstractChannelHandlerContext.java:340) >>>> at >>>> io.netty.channel.DefaultChannelPipeline$HeadContext.channelR >>>> ead(DefaultChannelPipeline.java:1334) >>>> at >>>> io.netty.channel.AbstractChannelHandlerContext.invokeChannel >>>> Read(AbstractChannelHandlerContext.java:362) >>>> at >>>> io.netty.channel.AbstractChannelHandlerContext.invokeChannel >>>> Read(AbstractChannelHandlerContext.java:348) >>>> at >>>> io.netty.channel.DefaultChannelPipeline.fireChannelRead(Defa >>>> ultChannelPipeline.java:926) >>>> at >>>> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.re >>>> ad(AbstractNioByteChannel.java:134) >>>> at >>>> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEven >>>> tLoop.java:624) >>>> at >>>> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimiz >>>> ed(NioEventLoop.java:559) >>>> at >>>> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEve >>>> ntLoop.java:476) >>>> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:438) >>>> at >>>> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(Sin >>>> gleThreadEventExecutor.java:858) >>>> at java.lang.Thread.run(Thread.java:745) >>>> Caused by: java.lang.NoSuchFieldError: INSTANCE >>>> at >>>> org.apache.activemq.artemis.core.protocol.mqtt.MQTTProtocolM >>>> anager.addChannelHandlers(MQTTProtocolManager.java:113) >>>> at >>>> org.apache.activemq.artemis.core.protocol.ProtocolHandler$Pr >>>> otocolDecoder.decode(ProtocolHandler.java:181) >>>> at >>>> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteT >>>> oMessageDecoder.java:411) >>>> ... 16 more >>>> >>>> >>>> So it seems that it is in fact a problem in Wildfly. >>>> Any idea where I could find the code for the artemis-integration in >>>> wildly? >>>> I don't find any branch/tag on >>>> https://github.com/apache/activemq-artemis/tree/1.x/artemis- >>>> protocols/artemis-mqtt-protocol >>>> for "artemis-mqtt-protocol-1.1.0.wildfly-017" >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805 >>>> .html >>>> >>> >>> >> > --001a113724b89b70fd055a1a84b5--