Tag Archives: performance testing

Initialization of the ALM Octane Server

If you are not getting past the initialization of the ALM Octane Server and getting database connection issues like

error: url=’jdbc:mercury:sqlserver://192.168.10.190:1433′, dbType=MSSQL, userName=’sa’]. Error: Connections could not be acquired from the underlying database!

The root cause for this is the SQL services.The SQL Agent and Browser are not running, causing the connection issue between the DB and the Octane server.

Advertisements

Copy test with requirement coverage

User wants to have all the test cases with the linked requirement from 3 different projects to one new project.

• Go to Management module (old projects)
• Go Libraries
• Create a new Library
o Select all the requirements
o Select ‘Test covering selected requirements’
• Create a baseline
o Check the logs

TARGET PROJECT:
• Import a library
• Check the logs
This copies the test and its requirement coverage as your user has requested.

The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index

Migrated our HP ALM to new windows server and sql server. Was able to migrate HP ALM to version 12.55 however projects fail to upgrade.

Getting the below error message after upgrading a project,

Exception occurred. Message: [Mercury][SQLServer JDBC Driver][SQLServer]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index name ‘LS_LOGICAL_NAME_IDX’. The duplicate key value is (hp.qc.plan-status.imported).
Failed SQL: /* ~~QC */ CREATE UNIQUE NONCLUSTERED INDEX [LS_LOGICAL_NAME_IDX] ON [LISTS]([LS_LOGICAL_NAME])

In this case the issue is because there is a duplicate key in [dbo].[LISTS] table.

You may need to run the following query in order to identify which is the duplicated one : select * from [dbo].[LISTS] where ls_logical_name=’hp.qc.plan-status.imported’

In this case it seems that the value for the LS_NAME had been modified, the default value is "Imported" and in your case is "Feedback Provided".

So the application notices the original value does not exist so it insets it (as seen in the last upgrade attempt, after running it another one was created) and consequently this causes the index duplicate error.

For fixing this issue it is necessary to update the LS_NAME to the original value, then run the upgrade process and later you can update the records again and have the customized as desired. This will not affect the data that is already in the entities .

After that you may need to follow the next steps in order to resolve the issue:

To update the records a simple query like this can be used:
Update [td].[LISTS] set LS_NAME ‘Imported’ WHERE LS_ID = ‘355’

HPE Diagnostics User Interface freezes or hangs

Having launched the HPE Diagnostics User Interface (UI) by clicking on “Open Diagnostics” (or “Open in This Window”) and entering a user name and password, performing an action such as viewing the data for long periods (days or weeks) for all Java Probes may result in the UI freezing and no further actions being possible. This issue may occur in a larger Diagnostics environment where there are many Mediators and numerous probes.

Once the Diagnostics UI has frozen no recovery is possible and the browser tab displaying the UI must be closed. The UI can then be opened in a separate browser tab (or new browser instance) however it is likely that the freeze behavior will re-occur.

A possible cause is that the Java applet which runs the Diagnostics UI has insufficient memory such that while the UI is performing the user action, the applet process runs out of memory and terminates. When this process terminates, the UI remains visible in the browser but is no longer functional.

To confirm that the Java applet process is terminating, open the Windows Task Manager and locate the process named “jp2launcher.exe”. This process will appear while the Diagnostics UI is being initialised (after the user name and password are validated):

image text

If the “jp2launcher.exe” is no longer visible when the Diagnostics UI freezes, then the process may have run out of memory.

A workaround for this issue is to increase the heap (memory) available to the Java applet. This can be done by modifying the Java runtime parameters as follows:

1) Open the Windows Control Panel and search using “Java” to locate the “Java (32-bit)” Control Panel entry. Click on the entry to open the Java Control Panel:

image text

Note: If there is no “Java (32-bit)” Control Panel entry this may be due to there being multiple Java versions installed on the client platform. Locate the Java 32-bit installed in a folder under “C:\Program Files (x86)” (typically “C:\Program Files (x86)\Java\jre7\bin”) and execute the file “javacpl.exe” using right-click “Run as administrator”.

2) Click on the “Java” tab and then on the “View” button to open the “Java Runtime Environment Settings” dialog.

3) The default heap size is typically 256MB however this may be system dependent. The actual process memory size can be seen in the Windows Task Manager before the process terminates. Specify a larger heap size and test to see if the UI freeze remains present – increase as needed. The following example confgure a 700MB heap however up to 1GB (“-Xmx1G”) may be used (as this is a 32-bit process memory is limited):

image text

Error -27732: Internal Error – can’t get initial credentials for username/password

The following error appears in web based protocol replay:

Error -27732: Internal Error – can’t get initial credentials for username/password

Wrong configuration of the required elements to make the script replay while using Kerberos authentication

Wrong username password:

  1. In the script go to the web_set_user function
  2. Verify that the username and password specified are correct

Wrong KDC IP:

  1. Open the windows environment settings
  2. Check the krb5.ini location specified in KRB5_COFIG
  3. Open the krb5.ini in an editor
  4. Check the KDC IP specified is as seen in wireshark recording of the application

Not able to start LR agent process with multiple terminal session

Not able to start LR agent process with multiple terminal session

Error logs while trying to start second Agent, just can start one Agent:
Error: Communication error: Failed to bind socket while calling bind function. [MsgId: MERR-10344]
19/02/2013 09:20:05 Error: Two Way Communication Error: Function two_way_comm_create_acceptor failed. [MsgId: MERR-60999]

Get inside agent configuration and click the check box for “Terminal Services”.  Not needed to use the Terminal Services side in the Controller, but it needs to be checked on the load generators.

Record IE 11 with Web (HTTP/HTML) protocol using TLS 1.1/1. 2 in VuGen 11.52

A hot fix has been created to enable:

  1. recording of Internet Explorer 11 and
  2. adding TLS 1.1 and TLS 1.2 support in VuGen 11.52

It can be downloaded using the below link: Download hotfix

Please follow the steps below to apply the hotfix:

  1. Go to the installation folder of LoadRunner, VuGen or Performance Center host
  2. Backup the original files in the bin and dat folders.
  3. Copy the hotfix files to the bin and dat folders respectively and replace the original files.
  4. Restart VuGen and try recording the business process in Internet Explorer 11 with TLS 1.1 and TLS 1.2 enabled in Internet Explorer Advanced Options.

Please note that the patch is needed for recording and should not be installed on Load Generator standalone machines.