Troubleshooting

🧩 Error	🧐 Cause	✅ Solution
`Connection to node -1 (<<kafka-host>>:9092) could not be established. Node may not be available.`	Kafka host is not resolvable.	Ensure the correct Kafka host is set in the configuration: `kafka { bootstrap.servers = "<<kafka-host>>:9092" }`
`Configuration file path does not exist: etc/jms-bridge/jms-bridge.conf`	Incorrect config file path.	Start the server with the correct configuration file: `etc/jms-bridge/jms-bridge.conf`
`AMQ222212: Disk Full! Blocking message production on address '<address-name>'. Clients will report blocked.`	Disk space has reached the configured limit.	Either free up disk space or increase the limit using: `<max-disk-usage>60</max-disk-usage>`

🧩 Error	🧐 Cause	✅ Solution
`Failed to create session factory. Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]`	Incorrect host or port in the connection string.	Verify the hostname and port: `connectionFactory.ConnectionFactory=tcp://localhost:61616`
Cross-platform Communication does not work	The topic name is missing the required Kafka prefix.	Add the `kafka.` prefix to the topic name: `kafka.<<topic-name>>`
JMS consumer fails to receive Kafka messages after server startup	Topic or queue not registered in address settings.	Ensure queues and topics are registered in `broker.xml` before server startup: `<addresses><address name="psy"><anycast><queue name="psy"/></anycast></address><address name="psy"><multicast><queue name="psy-1"/><queue name="psy-1"/></multicast></address></addresses>`
Messages are lost even when the topic or queue is registered	A non-durable consumer only receives messages while it is connected. Disconnected consumers will miss messages.	Use a durable consumer: `MessageConsumer consumer = session.createDurableConsumer(destination,"durableConsumer1");`
Client does not consume messages from backup server during failover	Only the live server is specified in the connection.	Include both live and backup servers in the connection string: `connectionFactory.ConnectionFactory=(tcp://<<live-jms-bridge>>:61616, tcp://<<backup-jms-bridge>>:61616)`