Troubleshooting Mid Tier cache issues

• If you turn on the ActiveLink logging, the Mid Tier presents a new cached object for the form.
• There might be an issue in the Mid Tier cache if the issue is resolved after enabling the ActiveLink logging, but reoccurs after you disable the ActiveLink logging. In this case, the issue is resolved if you clear the form from cache.
• If the issue persists even after enabling ActiveLink logging, then the issue can be at the AR Server. The issue can be in the object definition or in the AR Server Cache. You can take the following actions:
  • Export the form to a def file and share it with BMC Support.
  • Restart AR System server and check whether the issue is cleared from AR System server cache.

Refresh the Mid Tier cache.

Perform the following steps to refresh the Mid Tier cache:

• For an individual form:  
  Use the config_cache_cleanup.jsp utility.
• To clear the entire cache: 
  Use the Flush Cache button on the Cache Settings panel of Mid Tier Configuration Tool.

• To refresh cache and view statistics:
  Use the Hard Cache Flush procedure.
  For more information, see the knowledge article on BMC Communities How to flush the Mid-Tier cache.

Important: After each procedure, you must clear the browser cache before testing.

To understand the form HTML, form.js, and udd.js, related to a form, perform network capture when the form loads.

1. Enable detailed Mid Tier logs by using CACHE and PERFORMANCE log categories.
2. For more information, see Enabling-logs-for-Mid-Tier-troubleshooting.
   Detailed Mid Tier logging provides the perspective of Mid Tier processing. Mid Tier logs reflect any error in the Mid Tier caching process.
3. Perform tracelogging of the cached objects. For more information, see the following videos on YouTube.

Note: Unless you can access a specific Mid Tier and a specific AR System server, you must enable the Mid Tier logging on all user facing Mid Tiers and AR System servers that are behind a load balancer.

To disable the logging, use steps described in Enabling-logs-for-Mid-Tier-troubleshooting.

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 and tracelogger logs

Create a zip file of all logs at a location specified on the Log Settings page of Mid Tier Configuration Tool. 
For Microsoft Windows, the default location is:

C:\Program files\BMC Software\ARsystem\midtier\logs 

For Linux, the default location is:

/opt/bmc/ARsystem/midtier/logs

Collect and send logs with 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 that the user received
2. Collect the logs:
   • Create a zip file of each Mid Tier log set.
   • Create a zip file of each AR System server log set.
   • Create a zip file of the network capture file (*.har or *.saz file).

3. Attach the zip files to your case. You can attach files up to 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