DevTest IMS connect step is not closing TCP connections

book

Article ID: 196219

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

Virtual Service with IMS connect step encounters a WARN message in the vse.log if a request is sent from a specific IMS application:
WARN  com.itko.lisa.vse.stateful.protocol.ims.connect.IMSConnectProcessor - updateRequest
java.io.EOFException: Unexpected end of stream.

In addition netstat shows that connections are not released.
The VS works ok when sending a request from an IMS test in DevTest.

Cause

The header format of the IMS request was different to the supported 160-byte and 80-byte headers.
This was diagnosed with the help of a debug patch: patch_DE459263_10.3.0_DEBUG.jar

 

Environment

Release : 10.3

Component : CA Service Virtualization

Resolution

A custom IMS format needs to be configured in an ims.format file.
See:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/devops/devtest-solutions/10-3/using/using-ca-service-virtualization/using-devtest-workstation-with-ca-service-virtualization/creating-service-images/create-a-service-image-by-recording/transport-protocols/ims-connect-transport-protocol.html