This is what SoapUI reports, it's the same error as back in 2014 essentially, however the root cause is quite different.
As per Java 8 SDK Cryptography Architecture documentation...
Starting with JDK 8u31, the SSLv3 protocol (Secure Socket Layer) has been deactivated and is not available by default.
The above is due to the POODLE vulnerability. This setting is confirmed by looking at $JAVA_HOME/jre/lib/security/java.security file -
$JAVA_HOME/jre/lib/security/java.security
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 768, \
EC keySize < 224
Great, so SSLv3 is disabled.
Now according to WebLogic 12.2 documentation...
Not setting the weblogic.security.SSL.protocolVersion system property enables the SSLv3Hello, SSLv3, and TLSv1 protocols. In addition, for JSSE, all versions starting with "TLS" are also enabled.
However since the JDK specifically disables SSLv3, the above options are not available. The solution is to use TLSv1.1 or better TLSv1.2 when connecting. This is done by adding the line below to the vmoptions.txt file in SoapUI (/Applications/SoapUI-5.3.0.app/Contents/vmoptions.txt).
vmoptions.txt
-Dsoapui.https.protocols=TLSv1.2
I've tried and confirmed that the TLSv1 setting also doesn't work (presumably since it is also affected by POODLE). However, TLSv1.1 does work, as does the TLSv1.2.
-i