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

High Availability Log Messages

High Availability Log Messages

The
dxserver.log
file of each node in the network contains certain messages indicating that
dx-configuration.properties
file is configured properly.
The
message-broker/data/activemq.log
file on each node contains certain messages indicating that activemq.xml is configured properly.
If dx-configuration.properties under
B2B Data Exchange
server is configured properly the following messages (order may vary a bit) should be seen in dxserver.log of each node. In this example there are two hosts called host1 and host2 and the ports are
B2B Data Exchange
default ports.
INFO [org.apache.activemq.network.DiscoveryNetworkConnector] {Notifier-MulticastDiscoveryAgent-listener: DiscoveryNetworkConnector:localhost:BrokerService [b2bDxInternalCommandBroker]} Establishing network connection from vm://b2bDxInternalCommandBroker to tcp://host1:18100 INFO [org.apache.activemq.network.DiscoveryNetworkConnector] {Notifier-MulticastDiscoveryAgent-listener: DiscoveryNetworkConnector:localhost: BrokerService[b2bDxInternalCommandBroker]} Establishing network connection from vm://b2bDxInternalCommandBroker to tcp://host2:18050 INFO [org.apache.activemq.network.DemandForwardingBridge] {StartLocalBridge: localBroker=vm://b2bDxInternalCommandBroker:0#0} Network connection between vm://b2bDxInternalCommandBroker:0#0 and tcp://localhost/127.0.0.1:18100(b2bDxInternalCommandBrokerGUI) has been established. INFO [org.apache.activemq.network.DiscoveryNetworkConnector] {Notifier-MulticastDiscoveryAgent-listener:DiscoveryNetworkConnector: localhost:BrokerService[b2bDxInternalCommandBroker]} Establishing network connection from vm://b2bDxInternalCommandBroker to tcp://host2:18100 INFO [org.apache.activemq.network.DemandForwardingBridge] {StartLocalBridge: localBroker=vm://b2bDxInternalCommandBroker:0#2} Network connection between vm://b2bDxInternalCommandBroker:0#2 and tcp://host2/host2IP:18050(b2bDxInternalCommandBroker) has been established. INFO [org.apache.activemq.network.DemandForwardingBridge] {StartLocalBridge: localBroker=vm://b2bDxInternalCommandBroker:0#4} Network connection between vm://b2bDxInternalCommandBroker:0#4 and tcp://host2/host2IP:18100(b2bDxInternalCommandBrokerGUI) has been established.
If activemq.xml is configured properly then these messages should be seen on each node in the file
message-broker/data/activemq.log
:
INFO DiscoveryNetworkConnector -Establishing network connection from vm://localhost to tcp://host2:18616 INFO DemandForwardingBridge -Network connection between vm://localhost#0 and tcp://host2:host2IP:18616(localhost) has been established.

0 COMMENTS

We’d like to hear from you!