Troubleshoot unexpected Activator restarts

Unexpected Activator 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 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 <install directory>\conf\.
  2. Open log4j.properties 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 <install director>\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.

Windows

Use the Windows task manager to kill the cn (control node) and the Activator processes.

View the output files:

  • <install directory> /logs/ <machine_name_cn_console.log>
  • <install directory> /logs/ <machine_name>_console.log

UNIX

Use the following commands to kill the control node:

  • ps -ef | grep cn
  • kill -3 <pid>

View the output file: <install directory>/logs/<machine_name_cn_console.log>

Use the following commands to kill the Activator node:

  • ps -ef | grep te
  • kill -3 <pid>

View the output file: <install directory>/logs/<machine_name>_console.log

Related Links