(SOLVED! BY FAKING SYSTEM RANDOM GENERATOR, SEE BELOW)
I\'m setting up a VM image for my dev/build team. Inside that VM a Weblogic domain should be runn
SOLVED
Weblogic uses SecureRandom to init security subsystem. SecureRandom by default uses /dev/urandom device. For some reason, reading this device under VM comes to halt quite often. Generating console events helps to create more randomness, and release the WLS.
For the test purposes I have changed jre/lib/security/java.security file:
securerandom.source=file:/tmp/big.random.file
Weblogic now starts in 15 seconds.
Since we do not test any security stuff in our VMs, the repeating seed is totally alright for us.