Troubleshooting Integration Controller issues
Common Integration Controller issues
The following table lists issues that might occur while installing and using Integration Controller, and corresponding corrective actions to fix these issues.
Issue | Corrective action |
|---|---|
Unable to install Docker Engine | Upgrade the operating system. For more information about the system requirements for Integration Controller, see Installing-and-setting-up-the-connector-development-environment. |
Docker Compose fails to pull or start containers | Verify the Docker Engine and Docker Compose versions. For more information, see Installing-and-setting-up-the-connector-development-environment. |
Cannot connect to BMC Helix Integration Service from an on-premises network that is behind a proxy. Docker login fails during installation with the following error message: Error response from daemon: Get https://registry.integrate.bmc.com/v2/: dial tcp 54.209.152.200:443: getsockopt: connection refused |
|
The site goes offline, even though Integration Controller is installed and the same site was previously online | Restart Docker from your installation directory. Alternatively, use the validation utility to determine if the environment is set up correctly. For more information, see Validating-the-connector-development-environment. |
Primary or secondary controllers are offline frequently, and ActiveMQ connectors loses connection to the ActiveMQ on the cloud | This issue can occur if there is insufficent memory for the ActiveMQ to run the processes when a flow is executed. Complete the following procedure to customize the Java heap space and increase the memory limits: To customize the Java heap space and increase the allocated memory |
To customize the Java heap space and increase the allocated memory
- Locate reinitController script on your controller's system and open the script to edit.
- Locate an empty line after "fi" and before "$sh_c 'docker-compose down'" and add the following line in the located empty line:
echo -e "ACTIVEMQ_MIN_MAX=-Xms6G -Xmx6G" >> panama-on-premise.env
where -Xms is the minimum memory limit and -Xmx is maximum memory limit. In this case, the limit is set to 6 GB, and you can change the value as required. - Save the file.
- Enter the following command to run the reinitController scripts:
./reinitController - Then execute the following command:
docker logs panama-activemq - In docker logs search for "JVM args:"
- Make sure that activemq java startup command contains memory limits set in step 2. For example, if you set the limits to 6 GB, the JVM args should mention:
JVM args: -Xms6G -Xmx6G -XX:...
To access Integration Controller logs
For more information about the errors that might occur during Integration Controller usage, you can check the Integration Controller logs. To access them, perform the following actions:
- On the server where Integration Controller is installed, run the following command: docker ps
The list of all docker containers is displayed. Access the logs of a particular container by using the container name or the container ID, and running one of the following commands:
docker logs container_nameor
docker logs container_IDThe logs of the specified container are displayed.