Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Problem

For issues where workflow executions appear to be “hung” or “stuck” with statuses not being updated, it is helpful to the support team to receive thread dumps from the java processes used by FlexDeploy. These instructions provide details to collect the thread dumps for the FlexDeploy server JVM and the JVM which executes a plugin operation on an endpoint.

Solution

To generate the thread dump for the FlexDeploy server, you must first locate the process id (PID) of the underlying JVM.

ps -ef |grep flexdeploy

Now run the following command to signal the thread dump.

jstack

Download and attached the FlexDeploy logs to the support ticket.

To generate the thread dump for an endpoint, similarly you must locate the PID for the JVM running the plugin operation.

ps -ef |grep ExternalPluginServer

Signal the thread dump.

jstack

Download the log

  • No labels