Troubleshoot unexpected trading engine restarts

Unexpected Activator restarts may be due to:

  • Operating system issues
  • Product issues
  • Configuration issues

Analyze restart problems

Collect logs

The first step in troubleshooting is to collect trading engine logs, Activator logs and then analyze this data to identify the module that threw the first error.

Debug mode

If the logs and traces do not provide enough information, the next step is to run the servers in debug mode.

Activate Activator debug

  1. Go to <Activator_install_directory>\Activator\conf\.
  2. Open log4j2.xml in a text editor.
  3. Add the following lines:
    • log4j.category. b2bx.pluggabletransport=debug
    • log4j.category. b2bx.pluggabletransport.IntegratorPluggableServer=debug
    • log4j.category. b2bx.pluggabletransport.PluggableIntegratorClient=debug
  4. Save the file.
  5. Restart Activator.

To view Activator debug logs, go to <Activator_install_directory>\Activator\logs\ and open the file <machine name>_cn_console.log.

Generate and analyze dump files

Memory dump files record useful information that may help identify why a server has stopped unexpectedly.


Use the Windows task manager to kill the processes.

View the output files:

  • <Activator_install_directory>\ activator\logs\[ server_console.log]

Related Links