- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2016 10:15 AM
I am receiving "javax.net.ssl.SSLException: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: EC AlgorithmParameters not available" error when connecting to an outbound soap service in Geneva. My test application worked fine last week. I also tried from scratch in brand new Geneva and Helsinki instances, the same error in both environment. Everything works fine in SoapUI. What has been changed recently?
Thanks,
Henry
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2016 07:14 AM
A week after this problem was reported to the developer community, the problem seemed to be resolved by the ServiceNow.
Thanks for the help.
Henry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 06:37 AM
Hi Henry,
I have the same issue. Are you using developer instance requested by developer site?
My developer instance build: glide-geneva-08-25-2015__patch7-05-04-2016
But I tried it on some old instance with build: glide-geneva-08-25-2015__patch6-hotfix5-06-09-2016 and it works. Probably something with the patch.
This also look similar to this thread, so maybe try to ask also here:
Team Development Geneva upgrade connection issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 08:58 AM
Thanks Jakub, really appreciate your reply!
Yes, I am using developer instance build patch7. The wired thing is that everything works just fine last week. The only thing I can think of is that there might be some JRE changes on the backend (just guessing), which is out of our control.
Thanks again for your help.
Cheers,
Henry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2016 07:14 AM
A week after this problem was reported to the developer community, the problem seemed to be resolved by the ServiceNow.
Thanks for the help.
Henry