Troubleshooting

Troubleshooting ActiveMQ MPX

To determine whether your Microsoft Windows-based ActiveMQ MPX system is operating correctly, you can perform the following steps.

  1. Review the following configuration files to ensure that the server addresses and endpoints are correct:

    MPXEventTransmitter.xml

    For the Event Transmitter installed for each StarTeam Server.

    FileTransmitter.xml

    For the File Transmitter installed for each StarTeam Server.

    activemq.xml

    For each Message Broker.

    ActiveMQMessageBroker.ini

    For each Message Broker.

    RootCAConfig.xml

    For each Root MPX Cache Agent.

    RemoteCAConfig.xml

    For each Remote MPX Cache Agent.
  2. If they are not already running, start the Message Brokers.
  3. For each Message Broker you start, start a ActiveMQ MPX-enabled server configuration that communicates with that Message Broker.
  4. For each server configuration you start, review its server log file. If the Event Transmitter has any problems connecting to the Message Broker, the error messages will be written to the server log file (for example,Server.en-US.log), which is located in the root folder of the server configuration’s repository.
  5. Start a client and ensure that support for ActiveMQ MPX is enabled for your workstation.

  6. Enable client ActiveMQ MPX options:

    1. In your client, click Tools > Personal Options. The Personal Options dialog box opens.

    2. Select appropriate options on the Workspace and MPX tabs. The StarTeam Cross-Platform Client has MPX options on the Workspace tab. This option allows the StarTeam log file to include MPX information. The log file can be viewed at any time by clicking Tools > StarTeam Log. It also has settings for enabling and disabling MPX.

      Only the StarTeam Cross-Platform Client and IDEs based on StarTeam Cross-Platform Client and .NET components have options for MPX Cache Agent.

    3. Click OK. Test these settings.
  7. In your client, open a view from an ActiveMQ MPX-enabled server configuration. If MPX is enabled in both the client and the server configuration, a yellow lightning bolt appears in the status bar.
  8. Ensure that the machines running the different message brokers have their clocks synchronized. Failure to do this could cause message expiration and clients may not receive messages.

Back to top

Diagnosing a Message Broker

To assist with diagnosing problems, the Message Broker can generate logging information. To enable diagnostic tracing for the Message Broker, add the following lines to the STMessageBroker68.ini file: 

setopt trace_file c:\temp\mbtrace.txt
setopt trace_flags timestamp

After adding these lines and saving the file, restart the Message Broker to begin generation of the diagnostic messages. The messages are written to the trace file, prefixed with time stamp information.

Note: There may be some delay between the time a trace message is generated and when it is written to the log file. Consequently, the most recent trace messages may not appear until the Message Broker is stopped, allowing the file to be closed.

ActiveMQ MPX Message Brokers generate a log file named Activemq.log, located in data folder under the Message Broker installation folder. For example, at C:\Program Files\Micro Focus\ActiveMQ Message Broker\data.

Back to top