https://bz.apache.org/bugzilla/show_bug.cgi?id=58099
--- Comment #4 from Philippe Mouawad <[email protected]> --- (In reply to Sebb from comment #3) > The work-round seemed to work for me. At least some of the startup overhead > was reduced. I think this is because of the static{} block. > Read the thread on dev list called: httpClient.getConnectionManager() performance with HTTP only Oleg wrote this: ----------------------------------- I see. For the time what you can do is to use a custom SSL socket factory that lazily initializes SSL context when requested for the first time. This is exactly what HC 3.1 does. It will be somewhat slower given that one would need to mutex to synchronize access to the initialization code ----------------------------------- > What is the SSL code that is being invoked per thread? > I had a quick look and could not find anything SSL related apart from a call > to JsseSSLManager sslMgr = (JsseSSLManager) SSLManager.getInstance() which > is only done if the protocol is HTTPS. > > But perhaps I have missed something. -- You are receiving this mail because: You are the assignee for the bug.
