<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">In the URI's you're asking the shovel to connect on (i.e., "<a href="amqps://guest:guest@Server1">amqps://guest:guest@Server1</a>" and "<a href="amqps://guest:guest@Server2">amqps://guest:guest@Server2</a>"), 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.<div><br></div><div>Cheers,</div><div>Tim</div><div><br><div><div>On 29 Jan 2014, at 06:52, Tomas Tulka wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">At that point I'd guess a routing issue is to blame<br></blockquote><br>but if it is true, a message shouldn't have arrived to Server2 even in case<br>with no auth, but it does...<br><br>maybe it needs some additional setup on Server2...???<br><br><br><br>--<br>View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/shovel-with-authentication-tp32914p32930.html">http://rabbitmq.1065348.n5.nabble.com/shovel-with-authentication-tp32914p32930.html</a><br>Sent from the RabbitMQ mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br>_______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss<br></div></blockquote></div><br></div></body></html>