Increasing the heap size (virtual memory) for JBoss

For Windows, you can increase the heap size by uninstalling/reinstalling the Quality Center Service and modifying the InstallJbossService.bat file. For Linux/Unix, you need to modify the run.sh file. Recommended heap sizes, depending on the number of concurrent user sessions: Small: 128 - 256MB ~ Up to 10 concurrent user sessions Medium: 256 - 512MB ~ Up to 100 concurrent user sessions Large: 512 - 1024MB ~ Up to 250 concurrent user sessions Very Large: 1024 - 2048MB ~ Up to 350 concurrent user sessions Notes: The max value cannot be more than your max RAM size. On any Windows 32-bit installation you cannot set a heap size larger than 1024 MB of RAM. Uninstall/Reinstall QC Service for Windows: Note: Verify that users are not working on Quality Center and Quality Center Service is stopped. 1. Open Command Prompt and navigate to "<Drive Letter:>\program files\Mercury Interactive\Quality Center\jboss\bin" folder. Note: For Quality Center 9.0 and 9.2 the path is "<Drive Letter:>\program files\Mercury\Quality Center\jboss\bin"            For Quality Center 10 the path is "<Drive Letter:>\program files\HP\Quality Center\jboss\bin 2. Execute the following command (this will uninstall the existing service):    InstallJbossService.bat -uninstall 3.Edit the InstallJbossService.bat file. Example: If the heap memory is currently:    set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m increase the heap size as follows:    set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024m 4. Save and close the InstallJbossService.bat. 5. Execute the following command (this will install the service with the modified heap size parameter):    InstallJbossService.bat -c default (-help shows options) 6. Verify that the service has been installed, Control Panel -> Administrative Tools -> Services. 7. Start the Quality Center Service. 8. Check that the Quality Center Debug Console shows heap size that was specified as available memory: For Quality Center 9.0 and 9.2:    http://hostname:8080/qcbin/servlet/tdservlet?method=debuginfo    http://hostname:8080/sabin/servlet/tdsiteadminservlet?method=debuginfo For Quality Center 10:    http://hostname:8080/qcbin/debug Notes: If you are using a cluster environment, the hostname should be the cluster machine name, and you will need to apply the above steps to each cluster. Also edit the run.bat file to ensure it is synchronized with the way the QC service runs. Add the following parameter in site administration's 'Site Configuration' tab to grant access to the debug info log:      Name: DISABLE_CONSOLE_DEBUG_INFO      Value: N Modify the run.bat file: 1. On the application server, locate the JBoss bin folder under your TD for QC installation. By default, the location is <System Drive:>\Program Files\Mercury Interactive\Quality Center\JBoss\bin. Note: For Quality Center 9.0 and 9.2 the path is <System Drive:>\Program Files\Mercury\Quality Center\JBoss\bin.            For Quality Center 10 the path is <System Drive:>\Program Files\HP\Quality Center\JBoss\bin 2. Edit the run.bat file (or run.sh for Linux/Unix). Example: If the heap memory is currently:    set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx512m increase the heap size as follows:    set JAVA_OPTS=%JAVA_OPTS% -Xms512m -Xmx1024m 3. Save and close the run.bat. 4. Execute the run.sh file only for Linux/Unix.

Quality Center Performance Issue

Quality Center services will use 100% CPU utilization if we don't use the upload attachment functionality properly. This happens with patch 15. Below are details of the issue, work around and permanent fix.

1. Brief description of Attachment and Upload (Modifying attachment) functionality in QC
2. when this issue occurs
3. Issue Description
4. Steps to reproduce the issue (Manually)
5. Work around
6. Permanent fix
7. Upload button visibility (patch level comparison)
8. Conclusion

1. Brief description of Attachment and Upload (Modifying attachment) functionality in QC.

• Using Attach button we can attach a file which is available in physical directory of local machine to an entity.
• We can modify an attachment in the Attachments list. When you open an attachment in the associated entity, Quality Center downloads the attachment to a local directory on your client machine. After making changes, you must save the attachment twice. First, save it locally in the application in which you opened it. Then, in Quality Center, click the Upload Selected button to save the local copy of the attachment to your Quality Center project.  

2. When this Issue occurs

• If we click on Upload to attach a file after clicking Attach button which is not required.

3. Issue Description

• If the user is executing a test case and trying to use the upload button in a big project his/her browser will crash and they have to kill the IE process using Task Manager or restart the system and they can’t continue the same run even after logging in a new browser.
• For the above action QC will execute ListRepositoryFiles thread and will be continuously running until we restart the services.
• Below is the screen shot of the struck thread which is caused by this issue. If more number of users are trying to use this option our QC CPU utilization will reach 100%.

 4. Steps to reproduce the issue (Manually)

•  Login to project and click on Test Plan module. Select a test case
• which is in draft status  and click on Attachments tab and Click on Attach icon (fig.4.1) select the file which you want to attach.



fig.4.1







•  Once the attach is finished then select the file and click on Upload.
• Your browser will hang/Crash.
• Access the debug page (http://<server Name>:8080/qcbin/debug)  and you will find ListRepositoryFiles thread under current active Requests section.

5. Work around

• Disabling upload button while attaching a file using work flow script.
      Function ActionCanExecute(ActionName)
          if ActionName = "attach__upload" then
           msgbox "please don't click this button"
           ActionCanExecute = False
           exit function
          end if
          ActionCanExecute = True
      End Function
• If we apply the patch 20 which is in progress we don’t need to implement this code and it will be taken care by patch itself.

6. Permanent fix and Conclusion

• Increasing Jboss heap size which will resolve this issue.