Listeners operate as Java threads rather than as full requestors, and so cannot be accessed with the Tracer. Accordingly, use logs to debug listeners.
You can examine the log files by clicking Designer Studio> System >Operations> Logs> Log Files, or 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.
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 org.apache.logging.log4j.core.net.server.TcpSocketServer 8887 tcpSocketServer.properties
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 com.pega.pegarules.services Java package, or use the Logging Level tool to enable logging for this package temporarily.