-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rainer,
On 10/6/2009 2:00 PM, Rainer Jung wrote: > On 06.10.2009 17:41, Christopher Schultz wrote: > >> Another possibility is that SecureRandom is taking forever to >> initialize: if your JVM is configured to use a blocking source of >> entropy, that may be the problem. This often happens in *NIX >> environments, but it appears that you are running on Microsoft Windows, >> so that's unlikely to be the problem. > > ... and should only be a problem if SSL is involved. Doesn't Tomcat use SecureRandom for session id generation, at least under certain configurations? This would trip over a blocking entropy source regardless of SSL configuration, right? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrNBQMACgkQ9CaO5/Lv0PC5igCgjVbDsu74+cKSGW4geTCezF9r fE0An2X4LgJg8/jpkSV+Vgn+yjqdTpF/ =+3Ms -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
