[rabbitmq-discuss] shovel with authentization

[Jason McIntosh]

If the shovel is running you have a connection to the remote system (I
usually look at the web management interface to verify this, plus log
files).  At that point I'd guess a routing issue is to blame.  If you can
successfully publish a message to Server1 and then that message disappears
and never shows up on Server2.  You can try adding:
{publish_fields, [{exchange, <<"">>},{routing_key, <<"MyQ">>}]}
to your shovel configuration.  Of course make sure the routing/binding
works on both sides.  E.g. if you publish a message to Server2 that's
identical to the publish to Server1, does it show up in a Queue?

Jason



On Tue, Jan 28, 2014 at 9:29 AM, Tomas Tulka <tomas.tulka at atos.net> wrote:

> > Have you tried specifying certificate and keys as query parameters?
>
> I need only PLAIN auth and by the def. it should work with user:pass at host
> And I don't see a parameter for auth in URI query parameters.
>
> Auth works in general, because I am able to connect and send a message, the
> problem must be in the shovel
>
> Thx
>
>
>
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/shovel-with-authentication-tp32914p32916.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>



-- 
Jason McIntosh
https://github.com/jasonmcintosh/
573-424-7612
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140128/31cb55c4/attachment.html>