DevTest ITR cancelled causes Workstation to hang upto 30 secs

book

Article ID: 198528

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

When VSM or TEST is ran in ITR mode, then cancelled, workstation hangs for upto 30 secs. When checked workstation log, it has got below exception.

==========================================================================
| Exception: 
============================================================================
| Message:     callback
----------------------------------------------------------------------------
| Trapped Exception: User cancelled. Warning! External processes that are cancelled often leave irrecoverable side effects. You may need to close the application and start over.
| Trapped Message:   com.itko.util.swing.panels.ProcessingDialogCancelledException: User cancelled. Warning! External processes that are cancelled often leave irrecoverable side effects. You may need to close the application and start over.

Cause

The root cause for hanging upto 30 seconds is due to a code defect where, for an external DB configuration for Registry, if the DB is not reachable from Workstation and ITR is cancelled for the first time, a connection attempt was happening with certain connection url and waiting for 30 secs for the response. This hang does not happen if you re-run the same ITR again and again.

Also, the "Warning! External processes that are cancelled often leave irrecoverable side effects" message would get logged irrespective of the hang and is a message that user cancelled the ITR.

Environment

Release : 10.6

Component : CA Service Virtualization

Resolution

Open a support case and refer the defect number DE474674.

After receiving the patch files, use below steps to apply the patch:

1) Go to Workstation Machine.

2) Go to /lib/core/ directory.

3) Take backup of lisa-core-10.6.0.jar

4) Download the lisa-core-10.6.0.jar and replace.

5) Restart Workstation.

6) Test the scenario.

7) Better replace the jar in the Registry Machine as well and restart the registry.