>>>> Is there a way to reuse the SSL-session for several SOAP-Calls ?
As I've stated before it seems that soap over SSL sooner or later just fails. By activating the system property javax.net.debug (JSSE) it is clear that two independant sessions are created for each Call/SOAPHttpConnection. <<<< I just looked at SSLUtils for the first time. It calls startHandshake on the socket for each connection. I don't quite understand why: the comment mentions PrintWriter and exceptions, but PrintWriter is not used in HttpUtils, where the packets are written and read. I will look into this. >>>> As the call fails it is the response that fails (at least those times I've captured). Somewhere in between ClientHello and ServerHello for the response the SOAP client just assumes there is an answer but there is none so the client SOAP exception for "no http-status" is raised. <<<< This sounds bad. There may be a bug in the SSL implementation: too bad Sun does not provide source for us to look at. >>>> I don't think controlling the sessions would solve the problem (although it might be less frequent) but I suspect it would be beneficial from a performance point of view. <<<< I agree. When I get a chance, I will research startHandshake and possibly remove it and test the result locally. However, please understand that any change I might make will be in a release after 2.3.1, so if you are limited to using version 2.2, it won't help you. Scott Nichol -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
