Troubleshooting overall mid tier performance issues

Verify the Mid Tier and AR System server configuration.  For more information, see Health check from Remedy midtier perspective.

To understand the behavior of the Java Virtual Machine (JVM) supporting the Mid Tier, perform the following steps:

1. Gather thread dumps when the performance is slow or when the Mid Tier is not responding.
   Use the following options to take the thread dump:

   • Use the jVisualVM to gather thread dumps or heap dumps. For more information, see the knowledge article Remedy - Mid Tier - How to enable the Java JVisualVM process to collect logging

   • Use the Thread Dump feature on the Log Settings page of Mid Tier Configuration Tool. 
     This will create five separate thread dumps at a set interval.  The Mid Tier thread dumps are stored in the midtier/logs folder on the specific Mid Tier.
     

   • For Mid Tier versions earlier than 18.05, refer to the knowledge article Collect thread dumps in midtier without using JMX, jvisualvm or other third party tools

2. Fetch detailed Mid Tier logs by using SERVLET and PERFORMANCE log categories. For more information, see Enabling-logs-for-Mid-Tier-troubleshooting.
   Detailed Mid Tier logging gives a perspective of the Mid Tier to AR System server processing. You can track the HTTP request to the Mid Tier log and determine if the delay is due to Mid Tier.

1. Fetch Webserver logs. For more information, see Gathering-additional-logging-information.

Perform the steps listed in Enabling detailed Mid Tier logging and Enabling-server-side-AR-System-logs to disable the logging.

Remember to disable the logs from each Mid Tier and AR System server, on which logging was enabled.

Copy the logs to another location where you can review them so that they do not get overwritten.

The logs may be large depending on volume of activity during the logging period.

Collecting Mid Tier logs and thread dumps

Zip up all logs in the log location specified on the Log Settings page of Mid Tier Configuration Tool. 
For Microsoft Windows, the default location is as follows:

<Installation directory>\BMC Software\ARsystem\midtier\logs 

For Linux, the default location is as follows:

/opt/bmc/ARsystem/midtier/logs

For more information, see mid tier and webserver configuration files.

Collect and send logs and detailed information when creating a case with BMC Support:

1. Provide the following information as part of your case:
   • Name of the user who performed the search
   • The search criteria used
   • Time when the problem occurred
   • Any error messages received
2. Collect the logs.
   • Zip each Mid Tier log set.
   • Zip each AR System server log set.
   • Zip the network capture file. (*.har or *.saz file)

3. Attach the zip file to your case. You can attach zip files upto 2 GB. You can also upload the files on FTP.
   For more information, see Steps to send logs, files, screenshots, etc to BMC Support for a Remedy Product related case.

Mid Tier 9.x might stop responding due to logs

Mid Tier version 9.1.03 or later

Disable the Internal log category on the Log settings page of Mid Tier Configuration Tool.

Mid Tier 9x can become unresponsive due to logs

Mid Tier 9.1.02 or earlier

Upgrade to Mid Tier 9.1.03 or later.

With Midtier 9.1.02, the Sync Cache feature may cause server lockup or performance problems