SV VSE service Consuming 100% of CPU Utilization in DevTest 10.5-Response on the Wire HTTP/1.1 400 Bad request
search cancel

SV VSE service Consuming 100% of CPU Utilization in DevTest 10.5-Response on the Wire HTTP/1.1 400 Bad request

book

Article ID: 231044

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

SV VSE service Consuming  100% of CPU Utilization in DevTest 10.5 and seeing the Response on the Wire HTTP/1.1 400 Bad request in the logs. Not sure which VS is causing the 100% CPU. Also when VSE is restarted then the service comes back to normal position, but after sometime the VSE service again start consuming 100% of CPU Utilization.


2020-08-06 04:18:03,648Z (00:18)[PortServer:0.0.0.0/0.0.0.0:21000] INFO  - Response on the Wire HTTP/1.1 400 Bad request

Connection: close

Content-Type: text/html; charset=US-ASCII

<html><body><title>Bad Request</title><p>The following line is not a valid HTTP request:<p><pre> </pre></body></html>

2020-08-06 04:18:03,648Z (00:18)[PortServer:0.0.0.0/0.0.0.0:21000] INFO  - Response on the Wire HTTP/1.1 400 Bad request

Connection: close

Content-Type: text/html; charset=US-ASCII

 <html><body><title>Bad Request</title><p>The following line is not a valid HTTP request:<p><pre> </pre></body></html>

2020-08-06 04:18:03,648Z (00:18)[PortServer:0.0.0.0/0.0.0.0:21000] INFO  - Response on the Wire HTTP/1.1 400 Bad request

Connection: close
Content-Type: text/html; charset=US-ASCII

Environment

Release : 10.5.0

Component : DevTest Virtual Service

Cause

CPU Usage started spiking once Qualys scan started

Resolution

The patch resolves the High CPU issues caused by the Qualys scanner.  If anyone facing the same issue, please open a ticket with support and ask for "patch_DE501669_10.5.0_LTD.jar"

Below are the steps to apply the patch. 

1. Stop VSE and other Devtest services
2. Download and place the patch "patch_DE501669_10.5.0_LTD.jar" at LISA_HOME\lib\patches folder
3. Edit LISA_HOME\logging.properties file and add the following entries and save the file
        log4j.logger.NIOSession=TRACE
 
4. Add the following property to LISA_HOME\local.properties file
        com.itko.lisa.vse.sio.loggerName=NIOSession
 
5. Start all the DevTest Services.