TcpClientChannel - Channel Closed (smfclient x) - After Publishing Every Message to a Queue

[SeanTYH]

@Aaron

Hey there Inder. Ok, I don’t know camel-k that well, but I’ve seen similar issues in other JMS-using applications/frameworks (like Spring) where the connection is not cached… which causes a new connection to be made for every message. Definitely not ideal… you don’t want to be connecting/disconnecting all the time. You can verify these connects/disconnects are occuring by looking at the broker’s EVENT.LOG… if you can figure out how to get into the container’s shell (for docker: sudo docker exec -it /bin/bash) (for OVA: login with sysadmin and go into shell). Then navigate to /usr/sw/jail/logs/ directory and tail -f event.log.
Anyhow, see if you can find some camel-k configuration around caching your connection.
As for “creating topics” in Solace… that’s not how Solace really works… topics are pieces of metadata associated with each individual message… not something you configure on the broker. If you want persistent message flow, (typically) an administrator will configure a queue (in Solace, queue==persistent), and then add a topic subscription to that queue to attract messages.
Check out this video I made… it describes what topics are in Solace: https://www.youtube.com/watch?v=PP1nNlgERQI

I m facing the same issue (where solace is creating and closing many many TcpClientConnections) in Java, using Spring Boot. Is there any solution for this?