cAMQP requires the Client ID to be set - 6.2

Talend ESB Release Notes

Talend ESB
Installation and Upgrade
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Runtime
Talend Studio

When you use the cAMQP component in the Route Builder, make sure you always set the Client ID to a unique value which is not used in other Routes (the clientId header in cAMQP advanced settings.) If more than one cAMQP based Routes are executed in the same Talend Runtime container and the Client ID is not set, you will see some exceptions like:

org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Broker: localhost - Client: tlnd-spappala(6968):2 already connected from tcp://