Explanation of nio properties used DevTest

Products

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

Issue/Introduction

Have some properties used in DevTest but are not always shown in the local.properties or lisa.properties. 

Below are three that will need to get set to different values on occasion.

lisa.vse.tcp.uses.nio=true
lisa.vse.plain.tcp.uses.nio=false
lisa.vse.ssl.tcp.use.nio=false

Environment

All supported DevTest releases.

Cause

N/A

Resolution

"lisa.vse.tcp.uses.nio"

This property controls whether or not to use our non-blocking IO engine (NIO) when handling TCP traffic for virtual services.

It will do this for both plain TCP (non-SSL/TLS) connections and SSL/TLS over TCP connections.

The default for this property is true, which means we will use NIO for plain and SSL/TLS TCP connections.

 

"lisa.vse.plain.tcp.uses.nio"

This property is similar to the above, but it only controls whether or not to use NIO for plain (non-SSL/TLS) TCP connections.

"lisa.vse.ssl.tcp.uses.nio"

This property only controls whether or not to use NIO for SSL/TLS over TCP connections.

NOTE:

"lisa.vse.tcp.uses.nio" has the lowest priority and the "lisa.vse.plain.tcp.uses.nio" and "lisa.vse.ssl.tcp.uses.nio" will override it if set.

Setting both "lisa.vse.plain.tcp.uses.nio" and "lisa.vse.ssl.tcp.uses.nio" to the same value is the same as setting "lisa.vse.tcp.uses.nio" to that same value.