-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mansukhdeep,
On 6/27/12 11:00 PM, THIND Mansukhdeep wrote: > You were correct Chris. I found the jar file which was causing the > issue. It is a kernel specific jar that contains wrapper classes > for context initialization with the container/application server. > I removed it and viola, the server started up in 2 seconds.. :) Great. Thanks for following up -- next time, please post back to the list and not just to me. We are a community and not just a collection of individuals. > Unfortunately, now there is another problem. The application does > not allow the user to log in and create a session without that jar > being loaded. It is something I have taken up with people here at > DS. I guess you'll have to figure out what takes so long in the native portion of your library. We have seen lack of entropy in /dev/random (or equivalent) just blocking: basically, the CPU is just waiting for data to become available for, say, crypto operations. So, it looks like *nothing* is happening (which is true) but your process takes forever to accomplish its task. The solution on *NIX is generally to use /dev/urandom instead of /dev/random. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/s8voACgkQ9CaO5/Lv0PDq3gCfdp8qG20b7rdGBCyk05PLPjLF 5tkAnjphhcCP8pyvS4cM+aRnsEaqGINE =eESs -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
