SiKing

February 18, 2016

Another way to fix SSLHandshakeException in SoapUI

Filed under: automation,windows — SiKing @ 8:02 am
Tags:

Started testing a new API in SoapUI, and the very first thing I get is:

ERROR:Exception in request: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

So off I go, copy-paste the error into Google and see what comes up. There is a lot of advice about this issue here, here, here, none of which worked for me. Although this SO answer did lead me down the right path.

In the end, the problem was much more deluding.

Java comes with its own CA TrustStore. SoapUI, at least on Windows, comes with bundled Java, usually very outdated version of Java. From my past (Linux) experience I know that SoapUI is intelligent enough, that if it does not find the bundled Java it will look elsewhere ($PATH, $JAVA_HOME). So I went to my SoapUI install directory and renamed jre to jre.ignore. Of course I had previously installed the latest Java8. Restart SoapUI, and problem goes away.

I am not sure whom to blame for this WTF. Certainly part of the blame lies with Oracle lawyers for being dickheads (Java8 is not allowed to be pre-installed on any device), part lies with Microsoft for forcing their users to be ignorant retards, and part lies with SmartBear for following the crowd (the “every Java application must also install its own version of Java” crowd) like a sheep.

Advertisements

54 Comments »

  1. The only thing that eventually worked for me was to install and use the older version of SoapUI (5.3.0). In 5.4.0-EB I didn’t succeed and gave up 😦

    Comment by Adam — December 7, 2017 @ 7:14 am | Reply

  2. You DE MAN !!!!

    Comment by Anonymous — December 6, 2017 @ 8:08 am | Reply

  3. You are a one fantastic”o” dude

    Comment by Hasan — December 2, 2017 @ 6:34 pm | Reply

  4. Sorry to be the only one for whom it doesn’t work, but it doesn’t. I just reinstalled Windows 10 and downloaded SoapUI version 5.4.0-EB and the problem appeared (used 5.3.0 before and everything was ok). I installed most recent Java, renamed and then deleted the jre folder from soapui folder and i still get the Handshake exception. Not on every attempt, but on most. Now I REALLY have no idea where the problem is.

    Comment by Adam — November 30, 2017 @ 9:58 am | Reply

      1. If the issue is not consistent, then the problem could be somewhere else.
      2. Restart SoapUI, and try again. Make sure you see the message “INFO:Used java version: 1.8.0_144” (with the correct version) in the SoapUI log.
      3. Try the other links in the post.

      Comment by SiKing — December 1, 2017 @ 8:53 am | Reply

  5. Honestly…you’re a star Siking.

    Comment by Anonymous — November 30, 2017 @ 8:31 am | Reply

  6. Amazing solution that works!!!

    However now HermesJMS does not want to start from SoapUi window which used to work fine before. Where do I change the jre path that Hermes refers to? Checked hermes.bat but did not help me fix the problem

    Comment by Abhijith Madla — November 29, 2017 @ 8:09 pm | Reply

    • From HermesJMS homepage:

      Last Update: 2013-05-15

      Honestly I am surprised it still works at all!

      Comment by SiKing — November 30, 2017 @ 9:06 am | Reply

  7. Thanks so much! Solved my problem.

    Comment by beveradb — November 16, 2017 @ 2:03 am | Reply

  8. Awesome, thank you

    Comment by Anonymous — November 1, 2017 @ 11:37 am | Reply

  9. Really Awesome

    Comment by Ak — October 13, 2017 @ 6:37 am | Reply

  10. Thanks Man!

    Comment by Anonymous — October 13, 2017 @ 6:33 am | Reply

  11. Thanks a lot. Solved my problem.

    Comment by Anonymous — October 12, 2017 @ 11:07 am | Reply

  12. Thank you! Thank you! Thank you!

    Comment by Robert Paulsen — September 29, 2017 @ 2:10 pm | Reply

  13. Brilliant, been scratching my head and Googling for ages! Thanks 🙂

    Comment by Anonymous — September 29, 2017 @ 2:16 am | Reply

  14. thanks a lot , it really helped a lot 🙂 , can you please let us know how you got this solution ?

    Comment by sandeep — September 21, 2017 @ 12:39 am | Reply

  15. Worked like magic. Thanks!

    Comment by Anonymous — September 18, 2017 @ 5:33 am | Reply

  16. Thank you just ended 1 hour of feeling lost on internet.

    Comment by Anonymous — August 31, 2017 @ 12:04 am | Reply

  17. You are a genius. Even a novice non-technical person like me managed to get this working, very much thanks to your funny and insightful post. Just rename the directory and download java 8 and restart app and you should be golden. Thanks man.

    Comment by Anonymous — August 28, 2017 @ 1:36 pm | Reply

  18. Magic just happened. Thanks a ton for taking time and posting wonderful yet simple solution. If I meet you, I would like to give a treat to you 🙂

    Comment by Santosh — August 9, 2017 @ 2:03 am | Reply

  19. Worked for me too! Thank you for solid fix.

    Comment by Anonymous — August 7, 2017 @ 10:47 am | Reply

  20. Thanks a lot . It solved my issue . Great solution.

    Comment by Frank — August 7, 2017 @ 7:18 am | Reply

  21. Thank you very much for posting the solution.

    Comment by Anonymous — July 26, 2017 @ 7:38 am | Reply

  22. thanks it’s work for me

    Comment by yassine benaziz — July 6, 2017 @ 8:24 am | Reply

  23. Thank you… worked for me after days of struggling with it.

    Comment by Neetu — June 26, 2017 @ 11:19 pm | Reply

  24. Thanks dude – changing the jre to jre.ignore worked well for me.

    Comment by shamsu — June 5, 2017 @ 9:06 am | Reply

  25. I have 32-bit JRE installed in my machine and SOAP UI isn’t launching after renaming jre to jre.ignore. I have to use 32-bit for the application I am working on. Any suggestions?

    Comment by Chetan Chandrashekar — May 31, 2017 @ 2:42 pm | Reply

    • Install both 32b and 64b Java. To get SoapUI to pick up the 64b version, you have two options:

      1. Set JAVA_HOME to point to the 64b version.
      2. Edit soapui.(bat|sh) and hardwire the path in there.

      Comment by SiKing — May 31, 2017 @ 2:48 pm | Reply

  26. Perfect..thanks a ton..

    Comment by Anon — May 18, 2017 @ 10:07 pm | Reply

  27. perfect solution. you are a champ 🙂

    Comment by Anonymous — May 16, 2017 @ 1:18 pm | Reply

  28. Thanks..this option works really well..

    Comment by Anonymous — May 8, 2017 @ 6:47 am | Reply

  29. Thanks a lot

    Comment by Anonymous — May 3, 2017 @ 11:28 am | Reply

  30. I cannot thank you enough. I too went through several threads on the same issue, and you were the only one with the correct solution.

    Comment by Chris Gray — May 3, 2017 @ 8:41 am | Reply

  31. Awesome!! Solved the purpose

    Comment by Anonymous — April 26, 2017 @ 2:58 am | Reply

  32. That’s why you are The Champion. Worked great many thanks.

    Comment by Anonymous — April 24, 2017 @ 9:13 am | Reply

  33. Thank you So much! It worked 🙂

    Comment by Anonymous — April 16, 2017 @ 9:36 pm | Reply

  34. Thanks a Lot.

    Comment by Anonymous — March 22, 2017 @ 11:42 am | Reply

  35. Would have never figured this out on my own. The error doesn’t even infer a bad java config. Thanks!

    Comment by Anonymous — March 3, 2017 @ 2:32 pm | Reply

  36. Worked….so simple solution…thanks alot 🙂

    Comment by Anonymous — February 23, 2017 @ 10:57 am | Reply

  37. You are genius.I did not expect, this solution will work.

    Comment by Viplav — February 20, 2017 @ 2:05 am | Reply

  38. Genius! This fixed the issue I was having.

    Comment by Anonymous — February 13, 2017 @ 6:25 am | Reply

  39. Like a magic!

    Comment by Anonymous — February 2, 2017 @ 11:04 pm | Reply

  40. Thank you! Finally fixed the problem for me.

    Comment by Anonymous — December 13, 2016 @ 2:40 pm | Reply

  41. Best thing that happened to me today, spent a couple of hours checking out the other threads until I found yours. Thanks!

    Comment by Anonymous — November 24, 2016 @ 5:55 am | Reply

  42. This issue was wrecking my head for ages, thanks so much.

    Comment by Anonymous — November 11, 2016 @ 10:29 am | Reply

  43. Thank you! It works!

    Comment by Anonymous — November 8, 2016 @ 3:24 am | Reply

  44. Thank you !!!

    Comment by Anonymous — October 21, 2016 @ 8:21 am | Reply

  45. Thank you, saved my day!

    Comment by Anonymous — October 19, 2016 @ 11:32 pm | Reply

  46. Thanks God to take me here. I’m using JDK 8 and SOAP UI 5.2.1. None of the solutions worked. You saved me buddy. Have a nice weekend!

    Comment by Anonymous — September 30, 2016 @ 9:42 am | Reply

  47. God bless you bro!

    Comment by Anonymous — September 14, 2016 @ 6:15 am | Reply

  48. Thank you very much! It fixed my issue after days of struggling with it!

    Comment by Anonymous — August 10, 2016 @ 10:45 pm | Reply

  49. Thanks a lot, worked fine for me under windows 7 and JDK 8

    Comment by Anonymous — August 9, 2016 @ 7:30 am | Reply

  50. Thank you so much! Really appreciate you explaining this. Makes complete sense and I was able to fix my problem quickly.
    On OS-X, I renamed the folder /Applications/SoapUI-X.X.X.app/Contents/Plugins/jre.bundle to jre.ignore as you suggested.

    Comment by Anonymous — June 22, 2016 @ 2:23 pm | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: