Intermittent issues with a Virtual Service that is not responding to calls, only workaround is to re-deploy the Virtual Service
search cancel

Intermittent issues with a Virtual Service that is not responding to calls, only workaround is to re-deploy the Virtual Service

book

Article ID: 277836

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Running virtual services on a functional VSE.  Have one virtual service that after a time does not respond to calls and the only solution is to redeploy the virtual service.

Getting the below messages in the VSE and Registry logs.  Message "Transaction processing speed is being gated due to licensing restrictions" is misleading because the VSE is not exceeding 10 TPS.

 

VSE Log: 

[TEST_VIRTUAL_SERVICE [TEST_VIRTUAL_SERVICE]/1] WARN  com.itko.lisa.coordinator.VSETransactionLicensingManager - Transaction processing speed is being gated due to licensing restrictions

 

Registry log: 

2023-10-13T11:00:00,149Z (07:00) [ActiveMQ BrokerService[lisa3] Task-966] WARN  com.itko.activemq.broker.TransportConnector - Could not accept connection from tcp://IPADDRESS:PORT1: Remote host closed connection during handshake (SSL peer shut down incorrectly)
2023-10-13T11:00:00,171Z (07:00) [ActiveMQ BrokerService[lisa3] Task-966] WARN  com.itko.activemq.broker.TransportConnector - Could not accept connection from tcp://IPADDRESS:PORT2: Remote host closed connection during handshake (SSL peer shut down incorrectly)
2023-10-13T11:00:01,268Z (07:00) [ActiveMQ BrokerService[lisa3] Task-966] WARN  com.itko.activemq.broker.TransportConnector - Could not accept connection from tcp://IPADDRESS:PORT3: Remote host closed connection during handshake (SSL peer shut down incorrectly)
2023-10-13T11:00:01,291Z (07:00) [ActiveMQ BrokerService[lisa3] Task-966] WARN  com.itko.activemq.broker.TransportConnector - Could not accept connection from tcp://IPADDRESS:PORT4: Remote host closed connection during handshake (SSL peer shut down incorrectly)
2023-10-13T11:00:02,477Z (07:00) [ServerRequestResponder 19] INFO  System.out                     - Oct 13, 2023 7:00:02 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
2023-10-13T11:00:02,477Z (07:00) [ServerRequestResponder 19] INFO  System.out                     - INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?
2023-10-13T11:00:02,504Z (07:00) [pool-15-thread-2] INFO  System.out                     - Oct 13, 2023 7:00:02 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
2023-10-13T11:00:02,504Z (07:00) [pool-15-thread-2] INFO  System.out                     - INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?
2023-10-13T11:00:02,528Z (07:00) [qtp1124028832-85] INFO  System.out                     - Oct 13, 2023 7:00:02 AM com.squareup.okhttp.internal.Platform$JdkWithJettyBootPlatform getSelectedProtocol
2023-10-13T11:00:02,528Z (07:00) [qtp1124028832-85] INFO  System.out                     - INFO: ALPN callback dropped: SPDY and HTTP/2 are disabled. Is alpn-boot on the boot class path?

Environment

DevTest 10.7.2

Functional VSE

Cause

Product defect.

Resolution

Patch patch_DE571537_10.7.2_GA.jar

This patch will help solve the reported issue of some Virtual Services stopped working all of a sudden.

Steps to apply this patch:

1. Go to VSE Server
2. Stop VSE Service
3. Delete all the vse.log files.
4. Place the patch file 'patch_DE571537_10.7.2_GA.jar' in LISA_HOME/lib/patches folder (if a patches folder does not exists, create one.)
5. Start VSE Service