Overview

When you try to start a newly created Aurea Process instance with PostgreSQL and TomEE, it fails with a Failed to connect to broker exception error like below:

04-Feb-2021 09:21:36.577 SEVERE [EJBJmsResourceAdapter-worker- - 19] org.apache.activemq.ra.ActiveMQEndpointWorker$1.pause Endpoint will try to reconnect to the JMS broker in 30 seconds
04-Feb-2021 09:21:36.578 SEVERE [EJBJmsResourceAdapter-worker- - 21] org.apache.activemq.ra.ActiveMQEndpointWorker$1.pause Failed to connect to broker [tcp://qa.cx.aurea.com:16003]: Broker: qa.cx.aurea.com - Client: MonitorBean already connected from tcp://10.10.10.1:43906
javax.jms.InvalidClientIDException: Broker: qa.cx.aurea.com - Client: MonitorBean already connected from tcp://10.10.10.1:43906

The URL of the broker in the exception error is not the expected host and domain name for your new Aurea Process Instance even though you updated some of the server configuration files.

Solution

This issue occurs when a new Aurea Process instance is created by copying the files from the SBM_HOME directory of an existing Aurea Process instance.  If all of the required configuration files are not updated to use the correct host and domain name, an Aurea Process component will try to connect to the incorrect hostname for its required services.

To resolve this issue you will need to update all of the Aurea Process configuration files to use the correct host and domain name for the machine.