Re: JSS socket closing fix?

some other product, NSS maybe.) David.-Wan-Teh Chang wrote: ->To: "mozilla's crypto code discussion list">>From: Wan-Teh Chang  >Date: 02/15/2011 10:00AM >cc: David B Hinz  >Subject: Re: JSS socket closing fix? > >On Tue, Feb 15, 2011 at 8:19 AM, David B Hi

JSS socket closing fix?

 Was there a bug fix to JSS 4.2.5, 4.3, or 4.3.1 that dealt with a problem with sockets not being closed properly when a client application was shutting down? I thought I found a page or document indicating that a fix had been made for the above problem but I haven't been able to find the reference

Re: Re-reading certificates at runtime - Java

 Hi Glen, Thanks for the response.  I haven't had time to run the tests you suggested but hopefully this week I will be able to. > hi David,>> For JSS with SSLServerSocket if you want to do a reconnect because your > orginal cert you configured has expired> is now INVALID you would have to re-call

Re:Re-reading certificates at runtime - Java

See below for responses. David B Hinz wrote, On 2008-09-11 09:13: >> We are still encountering the problem detailed below that was described by >> Steve over a year ago. >> >> Is there anyone that can provide some insight on how we can solve this >> problem? &

Re-reading certificates at runtime - Java

We are still encountering the problem detailed below that was described bySteve over a year ago.Is there anyone that can provide some insight on how we can solve thisproblem?What happens is that some of our applications must run 24x7 yet the usercertificates are changed every 90 days (or sooner bas