Re: Artemis as multiprotocol broker

Good to hear. Have fun. On Thu, Aug 11, 2016 at 1:45 PM, Luca Capra wrote: > Martyn, > great work, I got connected and messages flows.. Thank you very much! > > Regards, > Luca > > 2016-08-11 11:23 GMT+02:00 Martyn Taylor : > > > No problem. Thanks for your help in identifying the issue. The

Re: Artemis as multiprotocol broker

Martyn, great work, I got connected and messages flows.. Thank you very much! Regards, Luca 2016-08-11 11:23 GMT+02:00 Martyn Taylor : > No problem. Thanks for your help in identifying the issue. The fix is now > merged on master you can check out the project and build it yourself. > > On linu

Re: Artemis as multiprotocol broker

No problem. Thanks for your help in identifying the issue. The fix is now merged on master you can check out the project and build it yourself. On linux: git clone g...@github.com:apache/activemq-artemis.git cd activemq-artemis mvn clean install -Prelease // This will install apache-artemis in

Re: Artemis as multiprotocol broker

Wow Martyn, thank you very much! So it is my browser (Chrome) causing the issue. Looking forward to test you fix. Best 2016-08-10 14:37 GMT+02:00 Martyn Taylor : > Hi Luca, > > The log message you were seeing is due to Artemis not supporting the > websocket subprotocol ID that is getting passed

Re: Artemis as multiprotocol broker

Hi Luca, The log message you were seeing is due to Artemis not supporting the websocket subprotocol ID that is getting passed in by the client. In my tests this didn't make a difference, the message was logged and the protocol carried on as normal. I see "CONNECTED" being logged in the console a

Re: Artemis as multiprotocol broker

Just to close the loop, the subprotocol name used by the library is *mqtt *for v3.1.1 Regards 2016-08-10 9:35 GMT+02:00 Luca Capra : > Hi Martyn, > thank you, indeed I corrected the client code (I exported the wrong code > with some paramters experiments) > > I prepared a running example here (o

Re: Artemis as multiprotocol broker

Hi Martyn, thank you, indeed I corrected the client code (I exported the wrong code with some paramters experiments) I prepared a running example here (output is all in the browser console) - This run the 1.3.0 version http://46.101.120.189/?url=mqtt://api.raptorbox.eu:1883 - This runs 1.4 snaps

Re: Artemis as multiprotocol broker

Hi Luca, The feature is supported. The issue was how you were configuring your client. There are two versions of MQTT that are supported in Artemis: 3.1 and 3.1.1. In 3.1.1 the protocol handshake (or ID), the first couple of bytes sent by the client changed. So, you must specify the correspond

Re: Artemis as multiprotocol broker

Hi Martyn, all sorry for taking on from such an old thread, but as of today with 1.4-SNAPSHOT I've not been able to have MQTT over websocket to work I continue to receive a debug notice like this - Requested subprotocol(s) not supported: MQTT - Requested subprotocol(s) not supported: mqttv3.1.1

Re: Artemis as multiprotocol broker

Hi Luca, You are seeing the error because you are not setting the correct version and protocol header in your client. Your client should set: ProtocolID="MQTT" and ProtocolVersion=4 // 3.1.1 or ProtocolID="MQlsdp" and ProtocolVersion=3 // 3,1 Artemis will accept both protocol versions (which

Re: Artemis as multiprotocol broker

Hi, I tried to setup the mqttjs library and run it in a browser. Unfortunately, it tries to connect over websocket and artemis cannot recognize the subprotocol The source is here: http://pastebin.com/Jgeijbz9 [Thread-10 (activemq-netty-threads-2076099910)] [DEBUG] io.netty.handler.codec.http.web

Re: Artemis as multiprotocol broker

Hi Martyn, I will bundle the js all in a page for testing. I think the js library will try to interact with "mqtt over websockets" from the browser. (See just one line above here, https://github.com/mqttjs/MQTT.js#contributing) Is it supposed to work in Artemis? (.. Nice feature btw!) I can eith

Re: Artemis as multiprotocol broker

Hi Luca, I had a play around with the JS you supplied but didn't get it working. Any chance you could browsify the test so I can run it without having a NodeJS environment set up, (A bash script would do if that's possible). I just need to see the issue in the broker. Thanks On Thu, May 26, 201

Re: Artemis as multiprotocol broker

Ok, I will double check on the client side. If you have the time, here the test case The nodejs client code https://gist.github.com/muka/b6374610618978948f39d83e5248ff7e The broker implementation (raptor-broker) is here (branch artemis) https://github.com/muka/raptor/tree/artemis To run it sh

Re: Artemis as multiprotocol broker

Hi Luca, Only 3.1.1 is supported in Artemis. We've not tested against older versions. Could you ensure you are setting the version properly in your client. Error processing control packet usually means the client is doing something wrong. If you send me your test case / reproducer, I will take

Re: Artemis as multiprotocol broker

Hi Martyn, thank you for your feedback! I had in fact two different acceptor on my broker.xml. I'm now using just one now. I've also moved to latest master 1.3-SNAPSHOT from git I noticed I get this exception now on connection via mqtt WARN: Error processing Control Packet, Disconnecting Client2

Re: Artemis as multiprotocol broker

Hi Luca, You don't need any specific configuration to do this. You can just set up a MQTT Client and a STOMP client and start sending/receiving from the same address. There are a couple of issues with Artemis versions <=1.2.0. I've fixed these issues on master and will be doing a 1.3.0 release

Artemis as multiprotocol broker

Hi all, on a project I'm working on I've switched from Apollo to Artemis. I'm running Artemis as an embed server and would like to have inter-protocol communication between stomp and mqtt. What I'm missing is if this can be done from configuration or creating an mqtt and stomp client each one to