OPS/MVS All releases
Component : MAINFRAME TEAM CENTER AUTOMATION
The deployment strategy involved cloning the MessageService Server to subsequent LPARs.
The Message Service Server was cloned from one LPAR to another. The hubnode.log showed where the messageServiceHubNode was "already connected." Corrected by deleting the brokerData and database directories in the cloned instance/MessageService directory. The following message was displayed in the hubnode.log:
javax.jms.InvalidClientIDException: Broker: messageServiceHubNode - Client: EMBEDDED_BROKER_3b8eed91-1b2d-459b-96ad-8c6f25d75aba_localhost_outbound already connected from tcp://###.###.###:##### (where ###.###.###:##### is the IPAddress)
This could occur in any release of the Mainframe Team Center Automation product component.