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

Compare with Current View Page History

« Previous Version 5 Next »

Sometimes we need to turn on access logs in Tomcat to check all the requests that DualShield receives.  This can be useful to resolve issues such as high CPU and server hang.

Tomcat is an Apache Server containing many services (in this case the components that make up DualShield.  The logs can be enabled on any of these services, however, typically we would enable them on just two; SSO  and DAC

Preparation

You will be making changes to the server.xml file which is located in C:\Program Files\Deepnet DualShield\tomcat\conf.  It is a good idea to make a backup copy of this file before commencing.

Enable Access logs for SSO and DAC

1) Stop the DualShield Server Service



2) Go to C:\Program Files\Deepnet DualShield\tomcat\conf

3) Edit server.xml in your preferred text editor and search for <Engine defaultHost="SSO" name="SSO">



4) Now search for AccessLogValve


5) You now need to modify this entry


5a) Start by uncommenting this section by deleting these two lines above and below


5b) Next, modify the following two parameters:

prefix="localhost_sso_access_log" 
pattern="%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i" "%{X-Dual-Tab-Id}i" "%{Cookie}i" "%{X-Forwarded-For}i""


 5c) The whole thing should now look like this…



Now Search for <Engine defaultHost="localhost" name="Catalina">



  1. Search again for AccessLogValve



  1. Carry out same changes as per Step 6) but for the Prefix use “localhost_DAC_access_log.”
  2. Save the server.xml file
  3. Restart the DualShield Server Service
  4. Wait for Service to fully start (CPU level low; Memory high)



  1. Check in the Tomcat Logs to see if a localhost_SSO_ access_log and localhost_dac_access_log file gets created.

 

  • No labels