search

apache / camel-kafka-connector

Camel Kafka Connector allows you to use all Camel components as Kafka Connect connectors
https://camel.apache.org
Apache License 2.0
152 stars 101 forks source link

amqps issue #1511

Closed Alexander-ac closed 1 year ago

Alexander-ac commented 1 year ago

Hi, I tried using amqps. No matter what I do, I'm unsuccessful.

I use the following components: camel-jms-amqp-10-source-kafka-connector-3.18.2-package.tar.gz apache-qpid-jms-0.55.0-bin.tar.gz

My configuration file looks like this:

name=CamelAmqpSourceConnector tasks.max=1 connector.class=org.apache.camel.kafkaconnector.jmsamqp10source.CamelJmsamqp10sourceSourceConnector camel.kamelet.jms-amqp-10-source.remoteURI=amqps://xxxxxxx.amazonaws.com:5671 camel.kamelet.jms-amqp-10-source.username=admin camel.kamelet.jms-amqp-10-source.password=secret camel.kamelet.jms-amqp-10-source.destinationType=queue camel.kamelet.jms-amqp-10-source.destinationName=SourceConnector topics=TEST_TOPIC key.converter=org.apache.kafka.connect.storage.StringConverter value.converter=org.apache.kafka.connect.storage.StringConverter

Can anyone tell me what I am doing wrong?

The following error occurs:

Could not refresh JMS Connection for destination 'Input.SourceConnector' - retrying using FixedBackOff{interval=5000, currentAttempts=1, maxAttempts=unlimited}. Cause: Client failed to authenticate using SASL: ANONYMOUS (org.apache.camel.component.jms.DefaultJmsMessageListenerContainer:1007)

orpiske commented 1 year ago

So, it failed to authenticate, but there should be a reason as to why that happened. If you can, increase the log level and provide the files (or at, least, a full stack trace).

Alexander-ac commented 1 year ago

Somehow I have the strong suspicion that the username and password have to be set elsewhere. I don't know how though. In the official description I didn't find any hints how to set username and password correctly. Can someone help me or give me a tip. Thanks in advance

Alexander-ac commented 1 year ago

I found the problem. However, the problem was different and the port was actually not activated in the firewall. The error message is definitely misleading at this point. The settings are correct. So I will close the ticket.