Disable Kafka If Necessary

If needed, you may disable Kafka communication, which might be preventing you from starting the application.

Kafka is used for communication with PlatformManager. Disabling Kafka will lead to inability to handle the IM instance in PlatformManager.

Problem

Assuming you have not configured the config server, you might get the following errors during the application startup:

10:55:22.213 | WARN  | kafka-admin-client-thread | adminclient-24 |  |  | o.a.kafka.clients.NetworkClient | [AdminClient clientId=adminclient-24] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available.
10:55:24.216 | WARN  | kafka-admin-client-thread | adminclient-24 |  |  | o.a.kafka.clients.NetworkClient | [AdminClient clientId=adminclient-24] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available.

This will lead to shutdown of the application.

Solution 1 - Connect Your App to Config Server

If you have proper access, you can get the Kafka configuration from the config server, which will result in successful connection to Kafka and your instance will be visible in IM.

Solution 2 - Disable Kafka

If you do not require Kafka, you can entirely disable it.

Ensure that you have not configured access to the config server (it might override your Kafka setup).
Set the property integration.event-driven.enabled=false either in application.properties or environment variables.