Default language.

Troubleshooting performance issues

When using , you might encounter certain performance issues such as  takes a long time to import the .def files or when you import or export a .def file, the import process stops responding. See the guidelines described here to troubleshoot performance issues with . Alternatively, you can create a BMC Support case.

Symptoms

  •  takes a long time to import .def files.
  • When you click any list or the All Objects list in AR System Navigator in , it takes 10-15 minutes to expand the list.
  • When you import or export a .def file in , the import process stops responding.

Scope

One or more users might experience the symptoms.

Resolution

Perform the following steps to troubleshoot performance issues with :

Step

Task

Description

1.

Review the configuration.

Verify that the Java path in the devstudio.ini file is correct. For more information, see the knowledge article 000309625.

2.

Unlock the workspace.

If  terminates abnormally, the workspace directory might get locked. If this occurs, restart  to unlock the workspace and to select or create another workspace.

3.

Review the  configuration.

In the devstudio.ini file, verify that the following items are correct:

  • Java heap size and maximum metaspace size
  • Java path for the -vm option

The following is a sample devstudio.ini file:

-clean

-vm C:\Program Files\Java\<Java_Home_Folder>\bin\javaw.exe 
-vmargs 
-Xms512m 
-Xmx2048m 
-XX:PermSize=64M 
-XX:MaxPermSize=256M 
-XX:+UseCompressedOops 
-Xverify:none 
-XX:+UseConcMarkSweepGC 
-XX:+CMSIncrementalMode 
-XX:+CMSIncrementalPacing

4.

Enable logs.

Enable Java debug logs for .

To know how to enable Java debug logging for the , see Enabling-Java-debug-logging-for-Developer-Studio or see the knowledge article 000210649.

Note: Enabling Java debug logging creates the javaapi.log file.

5.

Collect the logs.

Review the data in the log file to identify any symptoms or error messages.

The log file is located at: Users\Administrator\DeveloperStudio\workspace\.metadata.

metadata_log_file.JPG

Copy the log file to another location and then review it so that it does not get overwritten. The log file might be huge in size depending upon the volume.

See the table to troubleshoot issues based on the symptoms and error messages.

6.

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 faced an issue with 
    • Login information
    • Time when the issue occurred
    • Any error messages received
  2. Include the devstudio.ini file from the \BMC Software\ARSystem\DeveloperStudio folder.
  3. Collect the following log files:
    • arerror.log
    • javaapi.log (See step 4 in this table.)
    • Log file from the Users\Administrator\DeveloperStudio\workspace\.metadata folder.

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

7.

Analyze the log file.

You can review the log file to identify error messages or behaviors. See the table to identify the possible symptoms and solutions.

After you determine a specific symptom or error message, use the following table to identify the solution:

Symptom

Location

Action

Reference

When you click any list or the All Objects list in AR System Navigator in , it takes 10-15 minutes to expand the list.

On screen

Clear the  cache and retry expanding.

Related topic

Contacting Support

 

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