osdir.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apache camel - rabbitmq - ssl ( not working )


Pls advise on the possible causes of this or if more information is needed

On Mon, Mar 26, 2018, 11:24 PM Pranay Tonpay <ptonpay@xxxxxxxxx> wrote:

> I am trying to use apache camel ( camel-spring-boot - 2.20.2 ) with
> rabbitmq and create routes. It does work fine when iI use un-secured
> RabbitMQ ( no-SSL ), but when iI try to connect to RabbitMQ using SSL,
> it's not connecting to the queue at all. I am using "connectionFactory"
> option given on Apache Camel page. This connectionFactory object has all
> the correct parameters set (useSslProtocol, username, password etc ) Please
> note that the connectionFactory is properly populated, as iI am able to
> use it to connect using the other way (setting it in setConnectionFactory
> on SimpleMessageListenerContainer ). But with Apache Camel iI am facing
> issues.
>
> java.io.IOException: null at
> com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:116)
> ~[amqp-client-4.1.0.jar!/:4.1.0] at
> com.rabbitmq.client.impl.AMQChannel.wrap(AMQChannel.java:112)
> ~[amqp-client-4.1.0.jar!/:4.1.0] at
> com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:360)
> ~[amqp-client-4.1.0.jar!/:4.1.0] at
> com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:62)
> ~[amqp-client-4.1.0.jar!/:4.1.0] Caused by:
> com.rabbitmq.client.ShutdownSignalException: connection error at
> com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
> ~[amqp-client-4.1.0.jar!/:4.1.0] * * Caused by: java.io.EOFException at
> java.io.DataInputStream.readUnsignedByte(DataInputStream.java:290)
> ~[?:1.8.0_161] at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:91)
> ~[amqp-client-4.1.0.jar!/:4.1.0]
>
> While browsing more, iI came across this link Apache Camel SSL RabbitMQ
> <https://stackoverflow.com/questions/20332129/apache-camel-ssl-rabbitmq>
>
> but this seems to be a bit old, so may not be relevant anymore.
>
> Please advise. This has become a show-stopper for us.
>