To help you troubleshoot HTTP/TCP proxy problems, a number of logging methods are
available for the HTTP/TCP proxy.
Use these logs to troubleshoot problems with the HTTP/TCP proxy. For more
information, see Troubleshooting the HTTP/TCP proxy.
- HCL®
Quality Server
activity log
- Logs high-level messages to the Activity
log page in the
Administration page.
- To set the initial log level for the HTTP/TCP proxy, change
the
logger property in the
registration.xml file. For
more information, see Modifying the configuration settings of the HTTP/TCP proxy.
- To change the log level of the proxy while it is running, go
to the Infrastructure Dashboard in
HCL®
Quality Server, click the Log Level field for
the proxy, and select a value from the list.
- You can filter the activities based on the log level that are
displayed under the Activities
section.
- HCL®
Quality Server
diagnostic log
- Logs more detailed messages to the Diagnostic
log page on the
Administration page. The log
is disabled by default. When the log is enabled, it
contains the same information as the
java.util.logging file in a
format that you can access through HCL®
Quality Server. For more information, see Viewing the diagnostic log
and Enabling and disabling remote diagnostic logging for the HTTP/TCP proxy.
- java.util.logging (JUL) log file
- Logs detailed messages to a user-specified location.
- You can set the file location and logging level in the
proxy-logging.properties file.
The default log file location is
install/logs/proxy-n.log,
where install is the base
installation folder of the proxy server, typically the
httptcp directory in the
server installation directory.
- When the proxy runs as a Windows service, additional log
files are created in the logs directory related to the
service wrapper.
- To see any changes you make to the properties file, you must
restart the HTTP proxy.
Note: You can run the proxy from
the command line or as a service. In case you are
running it as a service, use file logging to
capture the logs.