Service Virtualization

Hi Team,

I have created one virtual Service and deployed. Some times it is not responding, getting Connection refused error.

I could see the below error in logs:

2018-06-11 19:39:57,327Z (15:39) [HTTP_AutoDepositRegistration [VS_VS_HTTP_AutoDepositRegistration_6_6_2018_Upd1_Run]/3] INFO  com.itko.lisa.test.TestCase    - Error doing destroy() on Step Virtual HTTPS Listener 12001: null
java.lang.NullPointerException.

Not sure what does this error mean? After redeploying the service, it is working fine.

Could you please look into error and let me know what might be the problem.

Thank you.

Rajasekhar

It shows as an INFO but not the ERROR. Can you share the compleate stack trace?

You also commented "Some times it is not responding, getting Connection refused error." This sounds as though the service is abnormally terminating (i.e., End the Test) and perhaps auto restarting. When you provide the logs having the destroy() message, can you also look for anything in the logs showing what happened several seconds prior to the timeslice where you see the Connection Refused error.

Hi Rajasekhar,

Did you read responses from Prema and Joel?

Could you please prepare the information that Prema and Joel requested?

Thanks Prema and Joel for the details.

Unfortunately I could not see any other details apart from this error. All VSE.log file contains this message only.

Thank you,

Rajasekhar

Hello Rajasekhar,

Is this still an issue for you?

If yes, please could you open a support ticket for this?

Thank you,

Heloisa

Hi Helosia,

I have updated the memory allocation in VSE and Registry vmoptions and restarted the services. I am not seeing this error now.

Not sure what was the issue.

Thank You.

Rajasekhar

Hi,

I have a similar question,

I have https service running in VSE1 and getting Read time out error. But if i deploy the same service with same port in VSE2 getting proper response with same port, and i have stopped the service in VSE1 before dploying in VSE2.

i same configuration for both the VSE's.   

Any idea?

BR

Venkata Yedida

Is this intermittent, getting Connection refused and error doing destroy(), and improved by increasing the amount of memory available to VSE? Or are you reliably getting a Read time out error on VSE1? It doesn't sound like a similar question, and I would first look at the differences in firewall settings on the two VSE server machines,  and then at the SSL configuration on the two VSE servers to see what's different.

No this is not intermittent.

I have allocated min 1024 M and max 2048M for VSE1.

I have 512M (min) and 1024M (max) for VSE2.

Both the VSE's on same windows server. it is a standlone setup.

Any update or thoughts on this why it is getting Read time out error?

You mention the 2 VSE's are running on the same Windows Server.

I personally would validate that this setup is not the cause of the issue? Have you assigned a unique port number to VSE2 via lisa.net.8.port property? If you stop the VSE1 process, then are you still not able to deploy the virtual service on VSE2?

Cheers,

Danny

i have assigned separate ports for VSE2.  i am able to deploy the vs in either of VSE's, But the server is working as expected in VSE2 but not in VSE1. when we hit the service in VSE1 it is throwing read time out error, before deploying in the VSE1 i have stopped the VS in VSE2.

Let me know if you have any queries. 

My question was have you stopped VSE2 (not only the virtual services inside). If only VSE1 is up and running does it still not work?

Is this error behaviour for every virtual service that you deploy in VSE1 or only for this specific one?

Cheers,

Danny

VSE1 running with VS and VSE2 is Stopped:    java.net.ConnectException: Connection refused: connect

VSE1 stopped and VSE2 running with VS:        proper response from VS

VSE1 running with VS in offline and VSE2 running with VS in online:  proper response from VS

VSE1 running with VS in online and VSE2 running with VS in offline:  java.net.SocketTimeoutException: Read timed out

this is the case with https services, but same VS which i have mentioned above is working fine with http.

Any idea why we are getting these errors?

DannySaro

No, no idea (yet), it obviously is not anything straightforward, this will have to focus on root-cause analysis.

The exception indicates that there is no service listening on the IP/port you are trying to connect to.

1. Assumption, you deploy the VS on VSE1, the portal indicates it is running just fine.

Can you assess by running netstat on your host running VSE1 that the VSE is listening on the specific port.

2. If nothing is listening on the port when running the VS in VSE1, can you look in the VSE1.log whether or not there are errors when deploying the virtual service.

3. If a process is listening on the port, then can try hitting the VS from a test case running in the workstation AND turn on HTTPS debug (can be found in Help menu item) and let us know what messages appear in the debug window

Cheers,

Danny

1. yes, it is running fine. I did netstat as well and it is listening on the port

2. it is ruuning

3. [ 1] ***
[ 1] found key for : lisa
[ 1] chain [0] = [
[ 1] [
[ 1] Version: V3
[ 1] Subject: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
[ 1] Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
[ 1]
[ 1] Key: Sun RSA public key, 1024 bits
[ 1] modulus: 107577342571485428802393728049184265786056348388364405824138117397977455761833138845329880593678805610027793821217939298848284286683543926634250841496293888229172692948746730869670908754188073542091973621265074265583182385560072567366227383567380577316296862528343858318946945517967854106447414857653511333997
[ 1] public exponent: 65537
[ 1] Validity: [From: Fri Aug 20 18:07:30 CEST 2010,
[ 1] To: Tue Jan 05 17:07:30 CET 2038]
[ 1] Issuer: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
[ 1] SerialNumber: [ 4c6ea842]
[ 1]
[ 1] ]
[ 1] Algorithm: [SHA1withRSA]
[ 1] Signature:
[ 1] 0000: 2B 7F 77 08 DE 2F 74 E3 CD 0F 58 D8 57 D9 08 2E +.w../t...X.W...
[ 1] 0010: AC 57 A7 02 81 07 B7 F8 5B 68 AE 22 22 C6 75 EE .W......[h."".u.
[ 1] 0020: C2 41 B6 23 DE ED 17 F8 21 AE 3B ED B6 EA 1A 17 .A.#....!.;.....
[ 1] 0030: A4 5F 95 FD BE AE 74 DA 75 64 19 D6 60 0A 63 61 ._....t.ud..`.ca
[ 1] 0040: B6 2A E1 FB 06 C5 36 E5 00 0C EB 20 EF FA 82 29 .*....6.... ...)
[ 1] 0050: 40 39 EA 61 3A 27 CF 4F 00 18 33 E8 31 4C E4 C5 @9.a:'.O..3.1L..
[ 1] 0060: 44 98 60 15 80 FE 85 FB BF BD 95 AB 35 14 F7 16 D.`.........5...
[ 1] 0070: 9D 58 F5 26 10 B7 76 7D 43 20 A7 4B F4 ED EE CF .X.&..v.C .K....
[ 1]
[ 1] ]
[ 1] ***
[ 1] X509KeyManager passed to SSLContext.init(): need an X509ExtendedKeyManager for SSLEngine use
[ 1] trigger seeding of SecureRandom
[ 1] done seeding SecureRandom
[ 1] ***
[ 1] found key for : lisa
[ 1] chain [0] = [
[ 1] [
[ 1] Version: V3
[ 1] Subject: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
[ 1] Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
[ 1]
[ 1] Key: Sun RSA public key, 1024 bits
[ 1] modulus: 107577342571485428802393728049184265786056348388364405824138117397977455761833138845329880593678805610027793821217939298848284286683543926634250841496293888229172692948746730869670908754188073542091973621265074265583182385560072567366227383567380577316296862528343858318946945517967854106447414857653511333997
[ 1] public exponent: 65537
[ 1] Validity: [From: Fri Aug 20 18:07:30 CEST 2010,
[ 1] To: Tue Jan 05 17:07:30 CET 2038]
[ 1] Issuer: CN=Lisa, OU=Lisa, O=Lisa, L=Dallas, ST=Texas, C=US, EMAILADDRESS=support@itko.com
[ 1] SerialNumber: [ 4c6ea842]
[ 1]
[ 1] ]
[ 1] Algorithm: [SHA1withRSA]
[ 1] Signature:
[ 1] 0000: 2B 7F 77 08 DE 2F 74 E3 CD 0F 58 D8 57 D9 08 2E +.w../t...X.W...
[ 1] 0010: AC 57 A7 02 81 07 B7 F8 5B 68 AE 22 22 C6 75 EE .W......[h."".u.
[ 1] 0020: C2 41 B6 23 DE ED 17 F8 21 AE 3B ED B6 EA 1A 17 .A.#....!.;.....
[ 1] 0030: A4 5F 95 FD BE AE 74 DA 75 64 19 D6 60 0A 63 61 ._....t.ud..`.ca
[ 1] 0040: B6 2A E1 FB 06 C5 36 E5 00 0C EB 20 EF FA 82 29 .*....6.... ...)
[ 1] 0050: 40 39 EA 61 3A 27 CF 4F 00 18 33 E8 31 4C E4 C5 @9.a:'.O..3.1L..
[ 1] 0060: 44 98 60 15 80 FE 85 FB BF BD 95 AB 35 14 F7 16 D.`.........5...
[ 1] 0070: 9D 58 F5 26 10 B7 76 7D 43 20 A7 4B F4 ED EE CF .X.&..v.C .K....
[ 1]
[ 1] ]
[ 1] ***
[ 1] X509KeyManager passed to SSLContext.init(): need an X509ExtendedKeyManager for SSLEngine use
[ 1] trigger seeding of SecureRandom
[ 1] done seeding SecureRandom
[ 1] Thread-77, setSoTimeout(30000) called
[ 1] Allow unsafe renegotiation: false
[ 1] Allow legacy hello messages: true
[ 1] Is initial handshake: true
[ 1] Is secure renegotiation: false
[ 1] Ignoring disabled protocol: SSLv3
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 for TLSv1
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_256_GCM_SHA384
[ 1] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_128_GCM_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_256_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_DH_anon_WITH_AES_128_CBC_SHA256
[ 1] Ignoring unsupported cipher suite: TLS_RSA_WITH_NULL_SHA256
[ 1] %% No cached client session
[ 1] *** ClientHello, TLSv1
[ 1] RandomCookie: GMT: 1543934010 bytes = { 57, 56, 63, 86, 180, 144, 163, 155, 235, 195, 145, 41, 197, 214, 134, 190, 252, 35, 217, 191, 119, 68, 219, 10, 34, 214, 138, 45 }
[ 1] Session ID: {}
[ 1] Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV, TLS_ECDH_anon_WITH_AES_256_CBC_SHA, TLS_DH_anon_WITH_AES_256_CBC_SHA, TLS_ECDH_anon_WITH_AES_128_CBC_SHA, TLS_DH_anon_WITH_AES_128_CBC_SHA, TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA, SSL_DH_anon_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_DH_anon_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA, TLS_ECDHE_ECDSA_WITH_NULL_SHA, TLS_ECDHE_RSA_WITH_NULL_SHA, SSL_RSA_WITH_NULL_SHA, TLS_ECDH_ECDSA_WITH_NULL_SHA, TLS_ECDH_RSA_WITH_NULL_SHA, TLS_ECDH_anon_WITH_NULL_SHA, SSL_RSA_WITH_NULL_MD5, TLS_KRB5_WITH_3DES_EDE_CBC_SHA, TLS_KRB5_WITH_3DES_EDE_CBC_MD5, TLS_KRB5_WITH_DES_CBC_SHA, TLS_KRB5_WITH_DES_CBC_MD5, TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA, TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5]
[ 1] Compression Methods: { 0 }
[ 1] Extension elliptic_curves, curve names: {secp256r1, sect163k1, sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1, sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1, sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1, sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}
[ 1] Extension ec_point_formats, formats: [uncompressed]
[ 1] ***
[ 1] Thread-77, WRITE: TLSv1 Handshake, length = 205
[ 1] Thread-77, WRITE: SSLv2 client hello message, length = 209
[ 1] Thread-77, handling exception: java.net.SocketTimeoutException: Read timed out
[ 1] Thread-77, called close()
[ 1] Thread-77, called closeInternal(true)
[ 1] [SSL Handshake Summary] Thread [Thread-77]
[ 1] [SSL Handshake Summary] Can not be sure if Client or Server
[ 1] [SSL Handshake Summary] *†‡ indicates linked optional steps
[ 1] [SSL Handshake Summary]
[ 1] [SSL Handshake Summary] 1 RUN Client Hello -->
[ 1] [SSL Handshake Summary] 2 UNKNOWN <-- Server Hello
[ 1] [SSL Handshake Summary] 3* UNKNOWN <-- Server Certificate (Public Key)
[ 1] [SSL Handshake Summary] 4† UNKNOWN <-- Request Client Certificate
[ 1] [SSL Handshake Summary] 5* UNKNOWN Verify and Trust Server Certificate v
[ 1] [SSL Handshake Summary] 6‡ UNKNOWN <-- Server Key Exchange
[ 1] [SSL Handshake Summary] 7 UNKNOWN <-- Server Hello Done
[ 1] [SSL Handshake Summary] 8† UNKNOWN Client Certificate (Public Key) -->
[ 1] [SSL Handshake Summary] 9† UNKNOWN v Verify and Trust Client Certificate
[ 1] [SSL Handshake Summary] 10 UNKNOWN Client Key Exchange -->
[ 1] [SSL Handshake Summary] 11† UNKNOWN Certificate Verify Confirmation -->
[ 1] [SSL Handshake Summary] 12 UNKNOWN Client Change Cipher Spec -->
[ 1] [SSL Handshake Summary] 13 UNKNOWN Client Finished -->
[ 1] [SSL Handshake Summary] 14 UNKNOWN <-- Server Change Cipher Spec
[ 1] [SSL Handshake Summary] 15 UNKNOWN <-- Server Finished
[ 1] [SSL Handshake Summary]
[ 1] [SSL Handshake Summary] java.net.SocketTimeoutException: Read timed out
[ 1] [SSL Handshake Summary] See Alert or Exception for details
[ 1] Thread-77, SEND TLSv1.2 ALERT: warning, description = close_notify
[ 1] Thread-77, WRITE: TLSv1.2 Alert, length = 2
[ 1] Thread-77, called closeSocket(true)

DannySaro

It is resloved, the service is using TLSv1, i found the difference in both the VSE's. it is working now. Thanks for your support.