That may explain why generating keyboard events release the server. I think I've got the track: it must be the randon seed initialization. Īnd here is the second, again up to 5 mins. Here we have the first delay, up to 5 mins. policy=/shared2/beahome/weblogic92/server/lib/weblogic.policy weblogic.Server Manifest_classpath =admin =wlsadmin -Dweblogic.Name=LOGMGR-admin curity W.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole=/shared2/beahome/patch_weblogic923/profiles/default/sysext_ =/shared2/beahome/weblogic92/server =/shared2/beahome/weblogic92/integration =true -Dwl shared2/beahome/jdk150_12/bin/java -client -Xmx256m -XX:MaxPermSize=128m -Xverify:none -da =/shared2/beahome/weblogic92 Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode) Here's the server output (just for a case): Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)

I wonder if others have the same problem? Was someone able to solve it? Here must be some developers who run WLS with a VM. WLST (Weblogic Jython shell) is also hanging for quite a time when executed in VM. Interesting that if I press Enter while looking at the stopped server, it wakes up much faster, sometimes after a few seconds.

Sleeping time is not constant, sometimes the server starts very fast, sometimes so-so, sometimes 10 minutes or more.

For tasks where deployment requires server restart it's very annoying. Two stops in total amount to about 10 minutes delay. I use Ububtu server distro, WLS 9.2MP3 + ALSB.Įverything works OK, quite fast, but at the start time the WLS stops twice for a measurable amounts of time. Inside that VM a Weblogic domain should be running. I'm setting up a VM image for my dev/build team. (SOLVED! BY FAKING SYSTEM RANDOM GENERATOR, SEE BELOW)

Virtualbox linux image mouse slow