[rabbitmq-discuss] shovel with authentization

[Tim Watson]

In the URI's you're asking the shovel to connect on (i.e., "amqps://guest:guest@Server1" and "amqps://guest:guest@Server2"), do the "Server1" and "Server2" portions refer to both the correct IP address *and* the correct port on which those RabbitMQ instances are listening for SSL connections? Your java code connects to 5671, which is typically the non-ssl port. If the shovel is trying to establish SSL connections (which is what the "amqps://" prefix means) on the wrong port, it will fail. I'd expect to see something in the logs though.

Cheers,
Tim

On 29 Jan 2014, at 06:52, Tomas Tulka wrote:

>> At that point I'd guess a routing issue is to blame
> 
> but if it is true, a message shouldn't have arrived to Server2 even in case
> with no auth, but it does...
> 
> maybe it needs some additional setup on Server2...???
> 
> 
> 
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/shovel-with-authentication-tp32914p32930.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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140129/e1e4b9f5/attachment.html>