Do you mean that the Apache SOAP server doesn't support keep-alives? Or the client?
I am finding that my attempts at writing a custom SOAP Transport are failing as well.. so perhaps you meant the former. This is frustrating.. I tried using pureTLS instead of JSSE.. no change.. so I think it's the JDK itself that is acting up. I am just surprised that this problem isn't higher profile!! It makes it unusable. I am finding 0 out of 10 times it is reusing the connection. Luke Galea Software Development BlueCat Networks 905-762-5225 -----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: February 5, 2003 9:57 AM To: [EMAIL PROTECTED] Subject: Re: Keeping socket open between calls Apache SOAP explicitly closes sockets after each request as it does not support HTTP keep-alives. The frequent handshaking is, I believe, caused by JSSE or JDK 1.4 marking cached sessions as stale very quickly. I have run tests in which a cached SSL session is re-used anywhere from 0 to 6 times out of 10. I have not figured out a way to control this. On 4 Feb 2003 at 11:42, Luke Galea wrote: > > Hello!! I am trying to make Apache SOAP keep my ssl socket open in > between calls in order to prevent un-needed handshaking. > > Has anyone had success doing something similar? I am currently trying > to use a custom SSLSocketFactorywithout much success.. perhapsa new transport would work? Why > isn(tm)t something like this included or available anywhere? > > Thanks in advance > > Luke Galea > Software Development > BlueCat Networks > 905-762-5225 > > Scott Nichol
