ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DevTest - Virtualizing Java Exceptions


Article ID: 108007


Updated On:


CA Application Test Service Virtualization CA Continuous Application Insight (PathFinder)


Virtualizing a Java Exception is different from virtualizing regular java classes.
You must virtualize the class throwing the Exception.

This document assumes the user knows how to virtualize regular java classes.


All supported DevTest versions.


Obtain and install the patched agent jars:
1. Open a support ticket to obtain the required agent patch. Reference DE358681
2. Replace the original agent jars with the new patched agent jars.
3. InsightAgent.jar must be used by the JVM. Currently, LisaAgent2.jar is not supported.
4. Restart the JVM where the agent is installed.
5. In the Portal, verify the agent's version number has been updated.
    Currently, the patched version is: This is the corrected patched agent version number for DevTest 10.2

To virtualize a Java Exception:
6. You can use either regular java virtualization method: Workstation Recorder or Intercepts in the Portal.
    See the DevTest documentation for each method to determine which method best fits your needs.
7. You much virtualize the class throwing the Exception. Not the Exception itself.
8. If using the Portal intercepts, make sure the Java and Exception protocols are set to full data.
9. Send transactions and capture the java class as normal.
10. If needed, send multiple transactions making sure to capture all required transactions types.
      Example with and without Exceptions.
11. Build and Deploy the Virtual Service as usual.
12. Test the Virtual Service


Additional Information

Not applicable.