[rabbitmq-discuss] Unable to establish MQTT plugin in rabbitmq version : 3.1.3.

[Ankur5 C]

Hi Michael,

I was going through the TLSConnection.java file .

Could you please clarify how exactly the SSL authentication happening ?

At the client side I have  client key.

I have done the server certificate trusting by importing only the server
certificate to the jvm keystore.

At the server side I have server certificates and keys and ca certificate.

My idea was like I need to have a ca certificate , client certificate and
client key at the client side (same as in the server side.)

How exactly the SSL handshaking happening ? Please clarify.



Thanks and Regards,
Ankur Chakraborty




From:	Ankur5 C/KOL/TCS
To:	Michael Klishin <mklishin at gopivotal.com>
Cc:	rabbitmq-discuss at lists.rabbitmq.com
Date:	01-07-2014 11:14
Subject:	Re: [rabbitmq-discuss] Unable to establish MQTT plugin in
            rabbitmq version : 3.1.3.


Hi Michael,

It worked . I removed the  {exchange,         <<"amq.topic">>}, part from
rabbitmq config file , now it is working fine.

Data are getting published.

Thanks again.

Thanks and Regards,
Ankur Chakraborty





From:	Ankur5 C/KOL/TCS
To:	Michael Klishin <mklishin at gopivotal.com>
Cc:	rabbitmq-discuss at lists.rabbitmq.com
Date:	01-07-2014 10:50
Subject:	Re: [rabbitmq-discuss] Unable to establish MQTT plugin in
            rabbitmq version : 3.1.3.


Thanks so much . I am also getting the same message but with an error .
Connection is established but then some error lines are displayed in log.

=INFO REPORT==== 1-Jul-2014::11:01:55 ===
accepting MQTT connection (127.0.0.1:57198 -> 127.0.0.1:8883)

=ERROR REPORT==== 1-Jul-2014::11:01:55 ===
connection <0.7519.1>, channel 1 - soft error:
{amqp_error,not_found,
            "no queue 'mqtt-subscription-paho-java-1qos1' in vhost '/'",
            'queue.delete'}

I guess there are some problems in the rabbitmq configuration file. Please
refer to my config file.

[{rabbit,        [{tcp_listeners,    [5672]},{ssl_listeners, [5671]},
			{ssl_options,
[{cacertfile,"/usr/lib/rabbitmq/testca/cacert.pem"},
                    {certfile,"/usr/lib/rabbitmq/server/cert.pem"},
                    {keyfile,"/usr/lib/rabbitmq/server/key.pem"},
                    {verify,verify_peer},
                    {fail_if_no_peer_cert,false}]}]},
 {rabbitmq_mqtt, [{default_user,     <<"guest">>},
                  {default_pass,     <<"guest">>},
                  {allow_anonymous,  true},
                  {vhost,            <<"/">>},
                  {exchange,         <<"amq.topic">>},
                  {subscription_ttl, 1800000},
                  {prefetch,         10},
                  {ssl_listeners,    [8883]},
                  {tcp_listeners,    [1883]},
                  {tcp_listen_options, [binary,
                                        {packet,    raw},
                                        {reuseaddr, true},
                                        {backlog,   128},
                                        {nodelay,   true}]}]}
].

Is something wrong here ? Please suggest.

Thanks and Regards,
Ankur Chakraborty





From:	Ankur5 C/KOL/TCS
To:	Michael Klishin <mklishin at gopivotal.com>
Cc:	rabbitmq-discuss at lists.rabbitmq.com
Date:	30-06-2014 14:59
Subject:	Re: [rabbitmq-discuss] Unable to establish MQTT plugin in
            rabbitmq version : 3.1.3.


Thanks so much , will try the same and let you know the updates.

Thanks and Regards,
Ankur Chakraborty




From:	Michael Klishin <mklishin at gopivotal.com>
To:	Ankur5 C <ankur5.c at tcs.com>
Cc:	rabbitmq-discuss at lists.rabbitmq.com
Date:	30-06-2014 14:28
Subject:	Re: [rabbitmq-discuss] Unable to establish MQTT plugin in
            rabbitmq version : 3.1.3.



 On 30 June 2014 at 12:53:28, Michael Klishin (mklishin at gopivotal.com)
wrote:
> > It works just like Paho Python and Ruby clients.

I've pushed all 3 examples I've used to GitHub:

https://github.com/michaelklishin/mqtt-tls-playground
--
MK

Staff Software Engineer, Pivotal/RabbitMQ


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you