Default language.

Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Troubleshooting overall midtier performance issues


When you observe performance issues of , use this information to either perform the appropriate logging and troubleshooting steps to resolve the problem or create a BMC Support case.


Related topics

Symptoms

  •  client is slow.
  •  client quits responding after running for a period of time.
  • Performance can be isolated to a specific .
  • Web server processes continue to run even though it is not responding to requests.

Scope

  • All users connected to the specific  experience the problem.

Diagnosing and reporting an issue

Step

Task

Description

1

Review the configuration

Verify the  and  configuration. See Health check from Remedy AR System Mid Tier perspective.

2

Determine the frequency of the performance issue


Determine the following:

  • Does the problem occur at start up only? 
  • Does the problem occur after running for a predictable interval?

3

Enable logs and reproduce the problem.

To analyze the JVM supporting the :

a)  Take thread dumps during the time of slowness or unresponsiveness. The following options are available:

b)  Enable detailed  logs by using the log categories: SERVLET, PERFORMANCE. See Enabling detailed Mid Tier logging.

  • Detailed  logging gives you the connection of the  to  processing. The HTTP request can be tracked to the  log to determine if the delay is in the  layer.

c)  Web server logs. See Gathering webserver logs.

4.

Disable the logging

Use similar steps as per the topic Enabling detailed Mid Tier logging to disable the logging enabled in the earlier step.

Remember to disable the logs from each  on which logging was enabled.

6

Collect the logs

 

Copy the logs to another location where you can review them so that they do not get overwritten. Remember the logs may be large depending on the volume of activity during the logging period.

 logs and  thread dumps:  Zip up the generated thread dumps and all the logs in the location specified on the  Config Tool - Log Settings. The default location is C:\Program files\BMC Software\ARsystem\midtier\logs for a Windows based  or /opt/bmc/ARsystem/midtier/logs for a Linux based .  

7

Creating a BMC Support Case

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 executed the action.
    • A description of the slow transaction.
    • The steps needed to trigger the action beginning at the login process. These steps need to be detailed on a step by step basis, documenting any data loaded or selected along the way.
    • Any error messages received.
  2. Gather the logs, thread dumps and config files from Step 6 into a zip file.
  3. Attach the zip file to your case (up to 2 GB) or FTP the files to BMC. See Steps to send logs, files, screenshots, etc to BMC Support for a Remedy Product related case.

8

Analyze the logs

You can review the logs yourself to try to identify error messages or behaviors.

Use the following table to troubleshoot based on your symptoms and error messages.


Error messages and resolution

Error

Where

Resolution

 9.x becomes unresponsive due to logs

 9.1.03 or better

Disable the Internal log category on the  config tool - Log settings.

Sync cache feature causes server lockup or performance problems

 9.1.02 or earlier

Upgrade to  9.1.03 or later.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 22.1