Activating Remote Debugging 

Use

In a cluster configuration, a debug node is integrated in the cluster until a debugging session is activated for it. Therefore, activating remote debugging results in the relevant debug node being isolated from the cluster. The message server then removes the node from the list of destinations and incoming requests can now no longer access the activated debug node. After activation, the debug node is no longer involved in cluster communication and must be restarted after the debugging session.

In a single server configuration (developer workplace) the server is stopped after debugging is activated is then fully reserved for debugging.

Prerequisites

The J2EE Engine is running and you have checked all prerequisites described in Preparing the Debugging Process.

Procedure

1. To display the J2EE Engine view, choose Window  → Show View → Other.
2. Choose J2EE  → J2EE Engine.
3. Choose OK.
4. In the J2EE Engine view that appears, expand the tree and select the relevant server process.

You might have to choose  Refresh tree to see it.

5. From the context menu of the selected server process, choose the action

Enable debugging of process in the single server configuration

or

Reserve process for debugging in the cluster configuration.

The process will restart. This may take some time.

6. Choose  Refresh tree to see updated status information.

If the process has restarted, Debug Mode is now ON.

Result

Now, this server node can be chosen for connection when creating the debug launch configuration.