I am seeing below error when I hit a service over https. I’ve tried changing TLS version in Soap ui VM options file as below:
-Dsoapui.https.protocols=TLSv1.0
-Dsoapui.https.protocols=TLSv1.2
and no luck. Please advise
Thu Sep 07 11:32:47 BST 2017:ERROR:javax.net.ssl.SSLException: Received fatal alert: protocol_version
javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flush(AbstractSessionOutputBuffer.java:138)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.flush(LoggingSessionOutputBuffer.java:95)
at org.apache.http.impl.AbstractHttpClientConnection.doFlush(AbstractHttpClientConnection.java:270)
at org.apache.http.impl.AbstractHttpClientConnection.flush(AbstractHttpClientConnection.java:275)
at org.apache.http.impl.conn.AbstractClientConnAdapter.flush(AbstractClientConnAdapter.java:197)
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:258)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:119)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:297)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:227)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Note: SoapUI version is 5.3.0 and Java version is
asked Sep 7, 2017 at 10:39
nari447nari447
7642 gold badges10 silver badges25 bronze badges
3
Please add -Dsoapui.https.protocols=SSLv3,TLSv1.2 to SoapUI-5.3.0.vmoptions file and it should solve the issue.
answered Apr 4, 2018 at 15:04
AGanAGan
4475 silver badges12 bronze badges
1
For those still unable to get SoapUI to work after altering your vmoptions file, here is the next thing to try.
Accourding to SiKing, the issue is with the provided version of Java bundled with SoapUI. SoapUI is smart enough to look for a local version if it can’t find its own, so simply renaming the jre folder solves the problem.
- Go to your SoapUI installation folder
- Rename the
jrefolderjre.ignore - Restart SoapUI.
This solved my problem.
answered Feb 5, 2019 at 22:12
Fix SSL error when you run SOAP UI
I have faced the same issue with the following error javax.net.ssl.SSLException: Received fatal alert: protocol_version in SoapUI. But resolved by adding https.protocols system property in the file SoapUI-5.3.0.vmoptions
- Open the file using Notepad.
- Add this protocol at the bottom “
-Dsoapui.https.protocols=SSLv3,TLSv1.2” and save the changes. - Close SOAP UI and relaunch. It works with no SSL error when you make API call. (Perform test ping call to check).
Add (-Dsoapui.https.protocols=SSLv3,TLSv1.2) in the VMOPTIONS file under the Bin folder. Eg:
C:SoftwaresSoapUI-5.3.0binSoapUI-5.3.0.vmoptions
-XX:MinHeapFreeRatio=20
-XX:MaxHeapFreeRatio=40
-Xms128m
-Xmx1000m
-Dsoapui.properties=soapui.properties
-Dsoapui.home=C:SoftwaresSoapUI-5.3.0/bin
-Dsoapui.ext.libraries=C:SoftwaresSoapUI-5.3.0/bin/ext
-Dsoapui.ext.listeners=C:SoftwaresSoapUI-5.3.0/bin/listeners
-Dsoapui.ext.actions=C:SoftwaresSoapUI-5.3.0/bin/actions
-Dwsi.dir=C:SoftwaresSoapUI-5.3.0/wsi-test-tools
-Djava.library.path=C:SoftwaresSoapUI-5.3.0/bin
-Djava.util.Arrays.useLegacyMergeSort=true
-splash:SoapUI-Spashscreen.png
-Dsoapui.https.protocols=SSLv3,TLSv1.2
Full error Log:
Mon Sep 14 07:47:30 CEST 2020:DEBUG:I/O error closing connection
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.SSLSocketImpl.checkEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.checkWrite(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flush(AbstractSessionOutputBuffer.java:138)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.flush(LoggingSessionOutputBuffer.java:95)
at org.apache.http.impl.AbstractHttpClientConnection.doFlush(AbstractHttpClientConnection.java:270)
at org.apache.http.impl.SocketHttpClientConnection.close(SocketHttpClientConnection.java:245)
at org.apache.http.impl.conn.DefaultClientConnection.close(DefaultClientConnection.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.close(AbstractPooledConnAdapter.java:152)
at org.apache.http.protocol.HttpRequestExecutor.closeConnection(HttpRequestExecutor.java:142)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:129)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:297)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:227)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:151)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.write(LoggingSessionOutputBuffer.java:74)
at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:114)
at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:120)
at org.apache.http.entity.ByteArrayEntity.writeTo(ByteArrayEntity.java:68)
at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:96)
at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:120)
at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:263)
at org.apache.http.impl.conn.AbstractClientConnAdapter.sendRequestEntity(AbstractClientConnAdapter.java:227)
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:255)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:119)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
... 14 more
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Closing the connection.
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Connection closed
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Connection shut down
Mon Sep 14 07:47:30 CEST 2020:ERROR:Exception in request: javax.net.ssl.SSLException: Received fatal alert: protocol_version
Mon Sep 14 07:47:30 CEST 2020:ERROR:An error occurred [Received fatal alert: protocol_version], see error log for details
Mon Sep 14 07:47:30 CEST 2020:INFO:Error getting response for [ScheduleSoap11.SendScheduleMessage:Request 1]; javax.net.ssl.SSLException: Received fatal alert: protocol_version
@See
- Java: javax.net.ssl.SSLException: Received fatal alert: protocol_version
- Apache Tomcat: javax.net.ssl.SSLHandshakeException: No appropriate protocol
8 How to fix SSL error when you run SOAP UI | Adobe Sign
answered Sep 14, 2020 at 6:48
YashYash
8,9902 gold badges67 silver badges72 bronze badges
You can configure supported versions of SSL in your SoapUI-5.3.1.vmoptions file, by adding a line e.g.:
-Dsoapui.https.protocols=SSLv3,TLSv1.2
answered Nov 22, 2018 at 0:55
I am seeing below error when I hit a service over https. I’ve tried changing TLS version in Soap ui VM options file as below:
-Dsoapui.https.protocols=TLSv1.0
-Dsoapui.https.protocols=TLSv1.2
and no luck. Please advise
Thu Sep 07 11:32:47 BST 2017:ERROR:javax.net.ssl.SSLException: Received fatal alert: protocol_version
javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flush(AbstractSessionOutputBuffer.java:138)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.flush(LoggingSessionOutputBuffer.java:95)
at org.apache.http.impl.AbstractHttpClientConnection.doFlush(AbstractHttpClientConnection.java:270)
at org.apache.http.impl.AbstractHttpClientConnection.flush(AbstractHttpClientConnection.java:275)
at org.apache.http.impl.conn.AbstractClientConnAdapter.flush(AbstractClientConnAdapter.java:197)
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:258)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:119)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:297)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:227)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Note: SoapUI version is 5.3.0 and Java version is
asked Sep 7, 2017 at 10:39
nari447nari447
7642 gold badges10 silver badges25 bronze badges
3
Please add -Dsoapui.https.protocols=SSLv3,TLSv1.2 to SoapUI-5.3.0.vmoptions file and it should solve the issue.
answered Apr 4, 2018 at 15:04
AGanAGan
4475 silver badges12 bronze badges
1
For those still unable to get SoapUI to work after altering your vmoptions file, here is the next thing to try.
Accourding to SiKing, the issue is with the provided version of Java bundled with SoapUI. SoapUI is smart enough to look for a local version if it can’t find its own, so simply renaming the jre folder solves the problem.
- Go to your SoapUI installation folder
- Rename the
jrefolderjre.ignore - Restart SoapUI.
This solved my problem.
answered Feb 5, 2019 at 22:12
Fix SSL error when you run SOAP UI
I have faced the same issue with the following error javax.net.ssl.SSLException: Received fatal alert: protocol_version in SoapUI. But resolved by adding https.protocols system property in the file SoapUI-5.3.0.vmoptions
- Open the file using Notepad.
- Add this protocol at the bottom “
-Dsoapui.https.protocols=SSLv3,TLSv1.2” and save the changes. - Close SOAP UI and relaunch. It works with no SSL error when you make API call. (Perform test ping call to check).
Add (-Dsoapui.https.protocols=SSLv3,TLSv1.2) in the VMOPTIONS file under the Bin folder. Eg:
C:SoftwaresSoapUI-5.3.0binSoapUI-5.3.0.vmoptions
-XX:MinHeapFreeRatio=20
-XX:MaxHeapFreeRatio=40
-Xms128m
-Xmx1000m
-Dsoapui.properties=soapui.properties
-Dsoapui.home=C:SoftwaresSoapUI-5.3.0/bin
-Dsoapui.ext.libraries=C:SoftwaresSoapUI-5.3.0/bin/ext
-Dsoapui.ext.listeners=C:SoftwaresSoapUI-5.3.0/bin/listeners
-Dsoapui.ext.actions=C:SoftwaresSoapUI-5.3.0/bin/actions
-Dwsi.dir=C:SoftwaresSoapUI-5.3.0/wsi-test-tools
-Djava.library.path=C:SoftwaresSoapUI-5.3.0/bin
-Djava.util.Arrays.useLegacyMergeSort=true
-splash:SoapUI-Spashscreen.png
-Dsoapui.https.protocols=SSLv3,TLSv1.2
Full error Log:
Mon Sep 14 07:47:30 CEST 2020:DEBUG:I/O error closing connection
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.SSLSocketImpl.checkEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.checkWrite(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flush(AbstractSessionOutputBuffer.java:138)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.flush(LoggingSessionOutputBuffer.java:95)
at org.apache.http.impl.AbstractHttpClientConnection.doFlush(AbstractHttpClientConnection.java:270)
at org.apache.http.impl.SocketHttpClientConnection.close(SocketHttpClientConnection.java:245)
at org.apache.http.impl.conn.DefaultClientConnection.close(DefaultClientConnection.java:164)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.close(AbstractPooledConnAdapter.java:152)
at org.apache.http.protocol.HttpRequestExecutor.closeConnection(HttpRequestExecutor.java:142)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:129)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:633)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:297)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:227)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:131)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:151)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.write(LoggingSessionOutputBuffer.java:74)
at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:114)
at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:120)
at org.apache.http.entity.ByteArrayEntity.writeTo(ByteArrayEntity.java:68)
at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:96)
at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:120)
at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:263)
at org.apache.http.impl.conn.AbstractClientConnAdapter.sendRequestEntity(AbstractClientConnAdapter.java:227)
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:255)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:119)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
... 14 more
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Closing the connection.
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Connection closed
Mon Sep 14 07:47:30 CEST 2020:DEBUG:Connection shut down
Mon Sep 14 07:47:30 CEST 2020:ERROR:Exception in request: javax.net.ssl.SSLException: Received fatal alert: protocol_version
Mon Sep 14 07:47:30 CEST 2020:ERROR:An error occurred [Received fatal alert: protocol_version], see error log for details
Mon Sep 14 07:47:30 CEST 2020:INFO:Error getting response for [ScheduleSoap11.SendScheduleMessage:Request 1]; javax.net.ssl.SSLException: Received fatal alert: protocol_version
@See
- Java: javax.net.ssl.SSLException: Received fatal alert: protocol_version
- Apache Tomcat: javax.net.ssl.SSLHandshakeException: No appropriate protocol
8 How to fix SSL error when you run SOAP UI | Adobe Sign
answered Sep 14, 2020 at 6:48
YashYash
8,9902 gold badges67 silver badges72 bronze badges
You can configure supported versions of SSL in your SoapUI-5.3.1.vmoptions file, by adding a line e.g.:
-Dsoapui.https.protocols=SSLv3,TLSv1.2
answered Nov 22, 2018 at 0:55
Содержание
- HTTPS requests with SoapUI and the HTTP Proxy Agent fail
- Troubleshooting
- Problem
- Symptom
- Cause
- Diagnosing The Problem
- Resolving The Problem
- SOAP UI – ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: получено фатальное предупреждение: handshake_failure
- SOAP UI – ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: получено фатальное предупреждение: handshake_failure
- E1: BSSV: Unable To Test BSSV with SoapUI On WebLogic 12.2.1 — «Error getting response:javax.net.ssl.SSLHandshakeException:Received fatal alert:handshake_failure» (Doc ID 2201709.1)
- Applies to:
- Symptoms
- Changes
- Cause
- To view full details, sign in with your My Oracle Support account.
- Don’t have a My Oracle Support account? Click to get started!
- Yashod’s Blog
- WebSphere Commerce 7 | SoapUI | REST Calls over HTTPS | SSLHandshakeException
HTTPS requests with SoapUI and the HTTP Proxy Agent fail
Troubleshooting
Problem
Attempts to use SSL with SmartBear SoapUI and the HTTP Proxy Agent of IBM Rational Test Control Panel (RTCP) yield «peer not authenticated» errors.
Symptom
After configuring SoapUI to use the HTTPS Proxy Agent on port 3129 you are unable to access HTTP sites.
No replies are received and SoapUI reports the following error at the bottom of the screen:
]Error getting response; javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Cause
SoapUI does not trust the self-signed certificate used by the HTTP proxy Agent.
You need to use HTTPS to access a system and cannot use HTTP.
Diagnosing The Problem
Check the SoapUI error log soapui-errors.log located in the bin folder.
On Windows systems this is typically: C:Program Files (x86)SmartBearSoapUI-4.6.4bin
Resolving The Problem
Refer to the SmartBear SoapUI documentation at http://www.soapui.org in conjunction with this technote. The configuration of SoapUI might change in the future.
There are two solutions to this problem:
- Configure SoapUI to trust the Proxy certificate
- Use the HTTP to HTTPS feature of the Proxy
SOAPUI CERTIFICATE TRUST:
- Exit from SoapUI.
Navigate to the SoapUI bin folder.
On Windows systems this is typically: C:Program Files (x86)SmartBearSoapUI- bin
Make a backup of file SoapUI- .vmoptions.
Navigate to the httptcp folder of an installation of RIT-Platform.
On Windows systems typically: C:Program FilesIBMRIT-Platformhttptcp
On non-Windows systems typically: /opt/IBM/RIT-Platform/httptcp
View the registration.xml file and note the keystore pass phrase. Search for keyStorePassword :
Copy the key store file greenhat.jks to the bin folder of SoapUI or a folder of your choice.
Edit file SoapUI- .vmoptions and add the following entries:
-Djavax.net.ssl.trustStore=greenhat.jks
-Djavax.net.ssl.trustStorePassword=
No path is required for trustStore if the file is placed in the bin folder.
Save the file and re-start SoapUI.
Click File > Preferences > Proxy Settings.
a) Click Manual for Proxy Setting.
b) Enter the hostname of the machine running the HTTP Proxy Agent.
c) Enter the port number of 3129 for HTTPS traffic
They will now be recorded.
If it is not possible or desired to modify the SoapUI configuration you can use the plain comms port of the HTTP Proxy. Port 3131 of the Proxy receives HTTP messages and re-sends them as HTTPS to the target system.
- Configure the SoapUI Proxy hostname, and port to be 3131.
Send HTTP messages using the correct port number.
Recording Studio will record the messages as the destination and port number match the recording rule.
If in doubt, go to the Agents page of the Rational Test Control Panel (RTCP) and click Show Rules to verify what is being recorded.
Источник
SOAP UI – ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: получено фатальное предупреждение: handshake_failure
Я пытаюсь попасть в сторонний веб-сервис с использованием SOAP UI и получить ниже исключения:
ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: Получено фатальное предупреждение: handshake_failure
Я не имею cacert или хранилище ключей от стороннего webservice, но у меня есть подпись. Используя подпись, я могу попасть в сторонний веб-сервис через мое приложение.
Как настроить эту подпись в пользовательском интерфейсе SOAP?
Добавление следующего параметра в C:Program FilesSmartBearSoapUI-5.2.1binSoapUI-5.2.1.vmoptions работало для меня.
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Быстрое исправление: SoapUI версию SoapUI версии 5.4.0. Это исправит проблему установления связи SSL.
После того, как я поместил ниже строку в файле SoapUI-5.2.1.vmoptions. Это работало нормально для меня.
Путь к файлу: SoapUI-5.2.1binSoapUI-5.2.1.vmoptions
Добавить под строкой:
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Это старая нить, но мое решение может помочь кому-то.
В SoapUI версии 5.3.0 я решил эту проблему, удалив строку:
из soapui.bat а затем с помощью soapui.bat для выполнения программы. Похоже, что Java, встроенная в SoapUI, отличается от моей версии JRE 1.8.0_131.
Для меня только ssl изменения не сработали.
это может отличаться от SOAP-UI JRE
в его случае попал в каталог smartbearSoapUI-5.2.1bin открыть soapui.bat
обновите совместимой версией Java, например:
закройте первую строку с помощью rem и обновите java dir.
Проблема в совместимости между вашей Java, установленной на вашем компьютере, и Java, которую мыло использует (для меня это SOAPUI-5.5.0)
SOAP UI не очень хорошо поддерживал последнюю версию Java.
Измените файл soapui.bat в (обычно установлен здесь)
C:Program Files (x86)SmartBearSoapUI-5.4.0binsoapui.bat
Вы можете увидеть там две строки:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
if exist “%JAVA_HOME%” goto SET_SYSTEM_JAVA
Первая строка SoapUi устанавливает каталог jre в каталог собственной папки
Вторая строка SoapUi говорит, что, если у вас установлена Java, используйте эту.
Так что вам просто нужно прокомментировать вторую строку следующим образом:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
rem, если существует “% JAVA_HOME%”, перейдите к SET_SYSTEM_JAVA
И для меня это работает там, где все другие виды действий (с разрешением TLS1.1 и т.д.) Не выполняются.
Источник
SOAP UI – ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: получено фатальное предупреждение: handshake_failure
Я пытаюсь попасть в сторонний веб-сервис с использованием SOAP UI и получить ниже исключения:
ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: Получено фатальное предупреждение: handshake_failure
Я не имею cacert или хранилище ключей от стороннего webservice, но у меня есть подпись. Используя подпись, я могу попасть в сторонний веб-сервис через мое приложение.
Как настроить эту подпись в пользовательском интерфейсе SOAP?
Добавление следующего параметра в C:Program FilesSmartBearSoapUI-5.2.1binSoapUI-5.2.1.vmoptions работало для меня.
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Быстрое исправление: SoapUI версию SoapUI версии 5.4.0. Это исправит проблему установления связи SSL.
После того, как я поместил ниже строку в файле SoapUI-5.2.1.vmoptions. Это работало нормально для меня.
Путь к файлу: SoapUI-5.2.1binSoapUI-5.2.1.vmoptions
Добавить под строкой:
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Это старая нить, но мое решение может помочь кому-то.
В SoapUI версии 5.3.0 я решил эту проблему, удалив строку:
из soapui.bat а затем с помощью soapui.bat для выполнения программы. Похоже, что Java, встроенная в SoapUI, отличается от моей версии JRE 1.8.0_131.
Для меня только ssl изменения не сработали.
это может отличаться от SOAP-UI JRE
в его случае попал в каталог smartbearSoapUI-5.2.1bin открыть soapui.bat
обновите совместимой версией Java, например:
закройте первую строку с помощью rem и обновите java dir.
Проблема в совместимости между вашей Java, установленной на вашем компьютере, и Java, которую мыло использует (для меня это SOAPUI-5.5.0)
SOAP UI не очень хорошо поддерживал последнюю версию Java.
Измените файл soapui.bat в (обычно установлен здесь)
C:Program Files (x86)SmartBearSoapUI-5.4.0binsoapui.bat
Вы можете увидеть там две строки:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
if exist “%JAVA_HOME%” goto SET_SYSTEM_JAVA
Первая строка SoapUi устанавливает каталог jre в каталог собственной папки
Вторая строка SoapUi говорит, что, если у вас установлена Java, используйте эту.
Так что вам просто нужно прокомментировать вторую строку следующим образом:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
rem, если существует “% JAVA_HOME%”, перейдите к SET_SYSTEM_JAVA
И для меня это работает там, где все другие виды действий (с разрешением TLS1.1 и т.д.) Не выполняются.
Источник
E1: BSSV: Unable To Test BSSV with SoapUI On WebLogic 12.2.1 — «Error getting response:javax.net.ssl.SSLHandshakeException:Received fatal alert:handshake_failure» (Doc ID 2201709.1)
Last updated on AUGUST 29, 2022
Applies to:
Symptoms
Using Weblogic 12.2.1. BSSV package was successfully built, deployed and BSSV WSDL can also be viewed using web browser.
However while running BSSV samples using SoapUI tools, it is showing following error —
Another symptom is that the WSDL will not load and error appears — Unable to Load URL.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don’t have a My Oracle Support account? Click to get started!
In this Document
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.
Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | 
| 
| 
| Legal Notices | Terms of Use
Источник
Yashod’s Blog
WebSphere Commerce 7 | SoapUI | REST Calls over HTTPS | SSLHandshakeException
And in my WebSphere Commerce logs, here is the error message,
[5/3/17 12:13:50:289 ART] 0000004e SSLHandshakeE E SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supported
at com.ibm.jsse2.kb.z(kb.java:241)
at com.ibm.jsse2.SSLEngineImpl.b(SSLEngineImpl.java:19)
at com.ibm.jsse2.SSLEngineImpl.c(SSLEngineImpl.java:169)
at com.ibm.jsse2.SSLEngineImpl.wrap(SSLEngineImpl.java:184)
at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:5)
at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:744)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:566)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:295)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1656)
Caused by: javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supported
Issue:
SoapUI is not enabled with TLS 1.2
Источник
Objective
SOAP UI (SmartBear) gets SSL connection error similar to the following one, which you get when you make API call. This error generally occurs if you are using outdated SSL or TLS protocol lower than TLS1.2
ERROR: Exception in request : javax.net.ssl.SSLException: Received fatal alert: protocol_version
ERROR: An error occurred [Received fatal alert: protocol_version], see error log for details
Steps
Steps to fix the error:
Add (-Dsoapui.https.protocols=SSLv3,TLSv1.2) in the VMOPTIONS file under the Bin folder.
-
Go to C:Program FilesSmartBearSoapUI-5.2.1bin (It depends on where you have installed the SOAP UI. It can be under C:Program Files (x86))
-
In the VMOPTIONS file, enable full read/write file permission.
-
Right click VMOPTIONS file>Properties>Security tab>Select User>Click Edit. (The User Access Control icon appears on the Edit button)>Select all the check boxes and click OK.
-
Repeat the same for Administrators, Systems, and all application packages.
-
Open the file using Notepad.
-
Add this protocol at the bottom “-Dsoapui.https.protocols=SSLv3 ,TLSv1.2 ” and save the changes.
-
Close SOAP UI and relaunch. It works with no SSL error when you make API call. (Perform test ping call to check).
Problem
Attempts to use SSL with SmartBear SoapUI and the HTTP Proxy Agent of IBM Rational Test Control Panel (RTCP) yield «peer not authenticated» errors.
Symptom
After configuring SoapUI to use the HTTPS Proxy Agent on port 3129 you are unable to access HTTP sites.
No replies are received and SoapUI reports the following error at the bottom of the screen:
]Error getting response; javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Cause
SoapUI does not trust the self-signed certificate used by the HTTP proxy Agent.
You need to use HTTPS to access a system and cannot use HTTP.
Diagnosing The Problem
Check the SoapUI error log soapui-errors.log located in the bin folder.
On Windows systems this is typically: C:Program Files (x86)SmartBearSoapUI-4.6.4bin
Resolving The Problem
Refer to the SmartBear SoapUI documentation at http://www.soapui.org in conjunction with this technote. The configuration of SoapUI might change in the future.
There are two solutions to this problem:
- Configure SoapUI to trust the Proxy certificate
- Use the HTTP to HTTPS feature of the Proxy
SOAPUI CERTIFICATE TRUST:
- Exit from SoapUI.
- Navigate to the SoapUI bin folder.
On Windows systems this is typically:
C:Program Files (x86)SmartBearSoapUI-<n.n.n>bin - Make a backup of file SoapUI-<n.n.n>.vmoptions.
- Navigate to the httptcp folder of an installation of RIT-Platform.
On Windows systems typically:
C:Program FilesIBMRIT-Platformhttptcp
On non-Windows systems typically:/opt/IBM/RIT-Platform/httptcp - View the registration.xml file and note the keystore pass phrase. Search for
keyStorePassword:keyStorePassword="<pass phrase here>" - Copy the key store file greenhat.jks to the bin folder of SoapUI or a folder of your choice.
- Edit file SoapUI-<n.n.n>.vmoptions and add the following entries:
-Djavax.net.ssl.trustStore=greenhat.jks
-Djavax.net.ssl.trustStorePassword=<pass phrase here>
No path is required for trustStore if the file is placed in the bin folder. - Save the file and re-start SoapUI.
- Click File > Preferences > Proxy Settings.
a) Click Manual for Proxy Setting.
b) Enter the hostname of the machine running the HTTP Proxy Agent.
c) Enter the port number of 3129 for HTTPS traffic - Start recording in RIT Recording Studio and send your HTTPS messages in SoapUI.
They will now be recorded.
HTTP TO HTTPS:
If it is not possible or desired to modify the SoapUI configuration you can use the plain comms port of the HTTP Proxy. Port 3131 of the Proxy receives HTTP messages and re-sends them as HTTPS to the target system.
- Configure the SoapUI Proxy hostname, and port to be 3131.
- Send HTTP messages using the correct port number.
For example https://someserver/someService would become http://someserver:443/someService.
Recording Studio will record the messages as the destination and port number match the recording rule.
If in doubt, go to the Agents page of the Rational Test Control Panel (RTCP) and click Show Rules to verify what is being recorded.
[{«Product»:{«code»:»SSBLQQ»,»label»:»IBM Rational Test Workbench»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Rational Integration Tester»,»Platform»:[{«code»:»PF016″,»label»:»Linux»},{«code»:»PF022″,»label»:»OS X»},{«code»:»PF033″,»label»:»Windows»}],»Version»:»8.0;8.5;8.6;8.7;9.0;9.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]
Вопрос:
Я пытаюсь попасть в сторонний веб-сервис с использованием SOAP UI и получить ниже исключения:
ОШИБКА: Исключение в запросе: javax.net.ssl.SSLHandshakeException: Получено фатальное предупреждение: handshake_failure
Я не имею cacert или хранилище ключей от стороннего webservice, но у меня есть подпись. Используя подпись, я могу попасть в сторонний веб-сервис через мое приложение.
Как настроить эту подпись в пользовательском интерфейсе SOAP?
Ответ №1
Добавление следующего параметра в C:Program FilesSmartBearSoapUI-5.2.1binSoapUI-5.2.1.vmoptions работало для меня.
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Проверьте эту ссылку
Ответ №2
Быстрое исправление: SoapUI версию SoapUI версии 5.4.0. Это исправит проблему установления связи SSL.
Ответ №3
После того, как я поместил ниже строку в файле SoapUI-5.2.1.vmoptions. Это работало нормально для меня.
Путь к файлу: SoapUI-5.2.1binSoapUI-5.2.1.vmoptions
Добавить под строкой:
-Dsoapui.https.protocols = TLSv1.2, SSLv3
Ответ №4
Это старая нить, но мое решение может помочь кому-то.
В SoapUI версии 5.3.0 я решил эту проблему, удалив строку:
if exist "%SOAPUI_HOME%..jrebin" goto SET_BUNDLED_JAVA
из soapui.bat а затем с помощью soapui.bat для выполнения программы. Похоже, что Java, встроенная в SoapUI, отличается от моей версии JRE 1.8.0_131.
Ответ №5
Для меня только ssl изменения не сработали.
Проверьте свой
Java-версия
это может отличаться от SOAP-UI JRE
в его случае попал в каталог smartbearSoapUI-5.2.1bin открыть soapui.bat
обновите совместимой версией Java, например:
REM set JAVA=%SOAPUI_HOME%..jrebinjava
set JAVA=D:Program Filesjavajdk1.8.0_162binjava
закройте первую строку с помощью rem и обновите java dir.
run
soapui.bat
Ответ №6
Проблема в совместимости между вашей Java, установленной на вашем компьютере, и Java, которую мыло использует (для меня это SOAPUI-5.5.0)
SOAP UI не очень хорошо поддерживал последнюю версию Java.
Измените файл soapui.bat в (обычно установлен здесь)
C:Program Files (x86)SmartBearSoapUI-5.4.0binsoapui.bat
Вы можете увидеть там две строки:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
if exist “%JAVA_HOME%” goto SET_SYSTEM_JAVA
Первая строка SoapUi устанавливает каталог jre в каталог собственной папки
Вторая строка SoapUi говорит, что, если у вас установлена Java, используйте эту.
Так что вам просто нужно прокомментировать вторую строку следующим образом:
if exist “%SOAPUI_HOME%..jrebin” goto SET_BUNDLED_JAVA
rem, если существует “% JAVA_HOME%”, перейдите к SET_SYSTEM_JAVA
И для меня это работает там, где все другие виды действий (с разрешением TLS1.1 и т.д.) Не выполняются.
I tried to use SoapUI tool for testing my WebSphere Commerce REST Services. It is working fine with HTTP URLs and not the HTTPS URLS and it is showing the following exceptions in SoapUI,
Wed May 03 16:42:27 ART 2017:DEBUG:Attempt 1 to execute request
Wed May 03 16:42:27 ART 2017:DEBUG:Sending request: POST /wcs/resources/store/10151/guestidentity?updateCookies=true HTTP/1.1
Wed May 03 16:42:27 ART 2017:DEBUG:I/O error closing connection
javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at sun.security.ssl.SSLSocketImpl.checkEOF(Unknown Source)
at sun.security.ssl.SSLSocketImpl.checkWrite(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
…….
…….
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(Unknown Source)
… 27 more
Wed May 03 16:42:27 ART 2017:DEBUG:Closing the connection.
Wed May 03 16:42:27 ART 2017:DEBUG:Connection closed
Wed May 03 16:42:27 ART 2017:DEBUG:Connection shut down
Wed May 03 16:42:27 ART 2017:ERROR:Exception in request: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
Wed May 03 16:42:27 ART 2017:ERROR:An error occurred [Remote host closed connection during handshake], see error log for details
Wed May 03 16:42:27 ART 2017:INFO:Error getting response for [https://localhost.guestidentity:Request 1]; javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake.
And in my WebSphere Commerce logs, here is the error message,
[5/3/17 12:13:50:289 ART] 0000004e SSLHandshakeE E SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supported
at com.ibm.jsse2.kb.z(kb.java:241)
at com.ibm.jsse2.SSLEngineImpl.b(SSLEngineImpl.java:19)
at com.ibm.jsse2.SSLEngineImpl.c(SSLEngineImpl.java:169)
at com.ibm.jsse2.SSLEngineImpl.wrap(SSLEngineImpl.java:184)
at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:5)
at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:744)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:566)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:295)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1656)
Caused by: javax.net.ssl.SSLHandshakeException: Client requested protocol TLSv1 not enabled or not supportedIssue:
SoapUI is not enabled with TLS 1.2Resolution to enabled the SoapUI with TLS 1.2,
1. Close the SoapUI
2. Open the following file, C:Program FilesSmartBearSoapUI-5.2.1binSoapUI-5.2.1.vmoptions
3. Add the following lines at the end,
-Dsun.security.ssl.allowUnsafeRenegotiation=true
-Dsoapui.https.protocols=SSLv3,TLSv1.2
4. Open the SoapUI again and it should start working,
