cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

How to resolve Glassfish bug causing AppDynamics Domain1 Service logs to grow rapidly

Symptoms

The AppDynamics Domain1 Service log (located in <Controller_Home>\appserver\glassfish\domains\domain1\bin\AppDynamicsDomain1Service.err.log) is growing rapidly when a Controller is installed on a Windows Server.

Diagnosis

There is a bug within Glassfish that causes this log file to grow rapidly.

 

This particular file contains the same information as the log files in <controller_home>/logs/server*.log files, so it is possible to rotate the Domain1 Service log without losing any data. 

 

Newer versions of Glassfish include an option to avoid writing any data to the Domain1 Service logs.

Solution

 

  1. Stop the Controller App Server
  2. Backup the Controller\appserver\glassfish\domains\domain1\bin\AppDynamicsDomain1Service.xml file
  3. Edit the XML file with the following changes:
    • Change from <logmode>reset</logmode> to <logmode>roll</logmode>.
  4. Start the App Server.

 


Note:  The log files are rotated with name .old not dynamically, but only on App Server start and stop. The logs will continue to grow until the next restart.

 

After these steps, the first time the App Server is restarted, the current log file will be renamed to .old. The next time the App Server is restarted, the .old file is purged and the current log file is renamed to .old.

 

Version history
Last update:
‎06-23-2017 09:43 AM
Updated by:
Labels (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.
0 Kudos