SSL Handshake Exception Error
I've been running into a problem very similar, if not identical, to the ones documented in these threads: http://www.eviware.com/forum/viewtopic.php?f=5&t=2533&hilit=ssl+handshake+error http://www...
Forum Discussion
Our team has discovered that the real bottleneck is the application of the synchronized keyword on SoapUIEasySSLProtocolSocketFactory.enableSocket, applied by Ole (see attachments). When removing the synchronized keyword, we were able to stress the server we were testing using SOAPUI w/o any ill-effects to SOAPUI. We have since noticed that SOAPUI developers (vladimir) have begun using Apache HttpClient 4.1 and replaced SoapUIEasySSLProtocolSocketFactory with SOAPUISSLSocketFactory (see attachments). Unfortunately, the synchronized keyword has been carried forward.
Our request is that the synchronized keyword be eliminated from the SOAPUISSLSocketFactory.enableSocket method, or an explanation be given as to why it is necessary. We have applied for the privs to write SOAPUI JIRA tickets to this end, but have not yet been given permission by SmartBear JIRA admins.
Thanks!
Our request is that the synchronized keyword be eliminated from the SOAPUISSLSocketFactory.enableSocket method, or an explanation be given as to why it is necessary. We have applied for the privs to write SOAPUI JIRA tickets to this end, but have not yet been given permission by SmartBear JIRA admins.
Thanks!
