Table of Contents

Search

  1. Preface
  2. Introduction to High Availability
  3. Set Up the High Availability Environment
  4. Set Up a High Availability Cluster on Windows
  5. Steps to Setting Up a High Availability Cluster in Linux
  6. Optional High Availability Configuration
  7. Appendix A: Troubleshooting High Availability
  8. Appendix B: High Availability Log Messages
  9. Appendix C: Port Number Reference
  10. Appendix D: Glossary

High Availability Installation Guide

High Availability Installation Guide

Troubleshooting High Availability

Troubleshooting High Availability

This section contains solutions to common problems that you might encounter when you configure a high availability cluster.
After installing and configuring the
B2B Data Exchange
server, the service does not start.
In the
startup.bat
or
startup.sh
file, change the value of the shutdown port to
28095
. The file is located in the following directory:
<
DX
InstallationDir>\
DataExchange
\bin
. If the cluster is installed on multiple hosts, change the value of the shutdown port on all the cluster hosts.
If the
B2B Data Exchange
JMS Broker service fails, pending messages are not released until the service starts again.
Restart the
B2B Data Exchange
JMS Broker service in all of the nodes in the cluster.
One of the services in the cluster failed.
Restart all of the
B2B Data Exchange
services on the node where the service failed.
After installing and configuring Managed File Transfer, the service does not start.
In the local_listener.xml file, change the HTTP or HTTPS listener port. For HTTP, change the default port from
5080
to the value
25080
. For HTTPS, change the default port from
5081
to the value
25081
. The file is located in the following directory:
<MFTInstallationDir>\hosts\local
The Dashboard displays the error message "Content was blocked because it was not signed by a valid security certificate."
Check that the URL defined for the Dashboard matches the URL used in the browser.
The Dashboard displays the error message "There was an error while processing your request."
In the
System Properties
page of the
B2B Data Exchange
Operation Console, ensure that the
dx.dashboard.url
property has the same URL as the
B2B Data Exchange
Operation Console web address.

0 COMMENTS

We’d like to hear from you!