-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neha,
Neha Agrawal wrote: |> Exactly how did you [build APR]? Are you sure you did it correctly? |> If you were recompiling, why not upgrade to the most recent version |> (1.2.12)? | | APR 1.2.7 package i downloaded and compiled it using | ./configure | make | make install This will not result in your apr using /dev/urandom. You need to do this: ./configure --with-devrandom=/dev/urandom ~From the ./configure help text: " ~ --with-devrandom[=DEV] use /dev/random or compatible [searches by default] " Any reason not to use 1.2.12 instead of 1.2.7? |> | and hence recompiled Native libraries |> | (because Native library builds with --with-apr-) |> What other native library? | | the tomcat-native libraries which are in tomcat's bin | folder, tomcat-native-1.1.6-src Since apr is used as a shared library, you shouldn't have to re-compile. It doesn't hurt, though. |> During that long pause, |> $ sudo lsof | grep '/dev/urandom' | gave: [several jsvc processes] No java processes? I'm not entirely sure how jsvc works... I had assumed it did an exec, which should change the process name. Do you see java processes in a ps listing, or only jsvc? I'm wondering if jsvc uses /dev/urandom for something unrelated. | Second instance: which is the one i have to get | working | i have configured it on 8180 port(http) | and 8443 port (Open-ssl, APR , native library stuff) | it also created two jsvc processes : root (1513) | and tomcat6 (1514) | this instance takes long time to restart after i try | to restart more than once. | ie. if i restart it once (after 8-10 hours) it | restarts instantly. That's because entropy is constantly collected from both devices. /dev/random blocks while /dev/urandom does not block (or generates a ton of entropy on short notice... i can never remember which). If there's not enough random source info to read from /dev/random, your computer will simply wait until enough is available. You can see from your own experience that it can take a very long time. |> grep "/dev/random" `find | /usr/lib/jvm/java-1.5.0-sun/` | gave: | Binary file | /usr/lib/jvm/java-1.5.0-sun/jre/lib/amd64/libapr-1.so.0.2.7 | matches | Binary file | /usr/lib/jvm/java-1.5.0-sun/jre/lib/amd64/libapr-1.a | matches Hmm... that's probably not good. Try recompiling with the configure flag I showed at the top of this post. | this means that libapr is still using /dev/random I think so. Another recompile should help. I built apr myself just now using --with-devrandom=/dev/urandom and I couldn't find /dev/random by grep'ing the binaries, while searching for /dev/urandom hit all of them. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke97f4ACgkQ9CaO5/Lv0PB+2QCfYRJmFBmu9zQ81kb/mk3M9l+J SzwAn35XzAZzZCQCi7OEWMXiieLhWN6M =YSpQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
