Error Connecting to Kafka from AEP | Community
Skip to main content
C
ChanuteJo
Level 3
May 13, 2025
Solved

Error Connecting to Kafka from AEP

  • May 13, 2025
  • 1 reply
  • 416 views

Dear community,

 

I was tasked with connecting Streaming Event Data into AEP using Kafka. I was following "This Link" (https://experienceleague.adobe.com/en/docs/platform-learn/tutorial-one-adobe/activation/rtcdpb2c/rtcdp26/ex2) "Link 2" (https://experienceleague.adobe.com/en/docs/platform-learn/tutorial-one-adobe/activation/rtcdpb2c/rtcdp26/ex3) and "Link 3" (https://experienceleague.adobe.com/en/docs/platform-learn/tutorial-one-adobe/activation/rtcdpb2c/rtcdp26/ex4). The first time I completed all these three links, I was able to finsih the exercise. The nex day, I was following the same steps and I was able to achieve the same results. However, one day when I try to access the connection, I was following the exact same steps but I ran into some errors. 

The following three steps what I have been using everytime I wants to restart Kafka connection each day. 
1. bin/zookeeper-server-start.sh config/zookeeper.properties ( in "This Link" or 2.6.2)

2. bin/kafka-server-start.sh config/server.properties (in "This Link" or 2.6.2) 

3. bin/kafka-console-producer.sh --broker-list 127.0.0.1:9092 --topic aep (in "Link 3" or  2.6.4)

 

The response I got from Command Prompt for each one is attached below for the latest Error Attempt is below and was unable to start Kafka. 

Have anyone ran into these problem before? If anyone knows how to resolve this issue and knows where I went wrong please help me resolve this issue. Do no hesitate to contact me if you need any further information from my side.

 

Best Regards,

Sching

Best answer by TylerKrause

Hey Sching!

I've never tried the connection with AEP specifically, but issues like this are very common with Kafka.

Have you tried checking the ports to see if they're occupied already?
On Linux/macOS, 'use lsof -i :<port_number>'. On Windows, use 'netstat -ano | findstr :<port_number>'

You can then kill the existing job with 'kill -9 <PID>' on Linux/macOS, 'taskkill /F /PID <PID>' on Windows.

If you have jobs running that you don't want to kill, you can try updating the ports for those jobs too. Zookeeper defaults to 2181 and Kafka Broker defaults to 9092. But you can update the ports based on the documentation outlined here: ZooKeeper: Because Coordinating Distributed Systems is a Zoo
Apache Kafka

Interested to see if either of these can solve your issue!

Best,
Tyler Krause


1 reply

TylerKrause
Adobe Champion
TylerKrauseAdobe ChampionAccepted solution
Adobe Champion
May 28, 2025

Hey Sching!

I've never tried the connection with AEP specifically, but issues like this are very common with Kafka.

Have you tried checking the ports to see if they're occupied already?
On Linux/macOS, 'use lsof -i :<port_number>'. On Windows, use 'netstat -ano | findstr :<port_number>'

You can then kill the existing job with 'kill -9 <PID>' on Linux/macOS, 'taskkill /F /PID <PID>' on Windows.

If you have jobs running that you don't want to kill, you can try updating the ports for those jobs too. Zookeeper defaults to 2181 and Kafka Broker defaults to 9092. But you can update the ports based on the documentation outlined here: ZooKeeper: Because Coordinating Distributed Systems is a Zoo
Apache Kafka

Interested to see if either of these can solve your issue!

Best,
Tyler Krause


    Terms & ConditionsAccessibility statement

    Loading footer...