Most implementations work fine with using /dev/urandom as a seed for the
sessionid generator for Tomcat (class ManagerBase), but I have 2 instances
that seem to cause Tomcat to hang on open of /dev/urandom. I have been
unsuccessful in finding any overrides that would get the session manager to
use something else for a seed. Do you know of any ways to get around this
problem without having to modify Tomcat classes? It appears that I should be
able to use an alternative class. The default is java.security.SecureRandom.
With Tomcat 3.3, I was able circumvent the problem by having Tomcat use
java.util.Random instead, but that does not seem to work on Tomcat 5.0.28.
Are you aware of any configuration options that would be suitable to
workaround the /dev/urandom hang?
