Table of Contents

Debugging listeners by using remote logging


Only available versions of this content are shown in the dropdown

For on-premises environments, you can troubleshoot listeners with more detail than is available using the Tracer by using remote logging.

You can examine the log files by using the Remote Logging feature to stream the contents of the log file to your workstation. You can watch the log as it grows while running a service rather than opening the log repeatedly.

Follow the steps in the following procedures to configure a listener or service requestor to send log messages to your workstation.

Install the log4j Remote Logging package

You can use the TcpSocketServer that comes with Log4j2. With TcpSocketServer, there is no user interface. You can control where incoming logs go using the same configurations as Log4j2. For more information, see the Log4j2 documentation. The following example shows how to configure and run TcpSocketServer:

startTCPSocketServer.cmd java -classpath .\log4j-api-2.5.jar;.\log4j-core-2.5.jar 8887

Modify logging settings

The prlog4j2.xml configuration file defines the levels of logging events. In a multinode system, you can create separate prlog4j2.xml files for each node.

When you are testing services, enable logging for the Java package, or use the Logging Level tool to enable logging for this package temporarily.

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.