It takes upwards of 15 minutes to fully start the admin server on my Windows box. I have read that it's a bug in the Java security random number/crypto api.
There are various work arounds for the Linux environments, but no mention of Windows. I realize that I'm in a small minority of admins running WLS on Windows, but does anybody have experience in setting the Java security stuff so the servers do not take soooooo darn long to startup?
Can you please give some more details as in at what point does the WLS Admin server start up hang up as in takes the most time ?
I have WLS Admin installed on windows but haven't seen thins kind of issue yet .
I can't really tell where it slows down. When I look at the admin console messages, there is very little action. It's like every step takes a long time.
The java.exe process hosting the AdminServer increases in memory from 0 to about 600MB and it takes about 10-12 minutes before the server gets to "RUNNING mode".
When you fire up your admin server, how long does it take to get fully started?
Edited by: JDM on May 8, 2012 9:50 AM
I think it would be better to post this question in the Weblogic - General forum for WLS specific troubleshooting tip : WebLogic Server - General
Having said that get the thread dump for WLS server start up using kill -3 <pid> command or using jstack -l <pid> .
Post the question and the thread dumps to the above mentioned forum .
In my case the start up time is less than a minute .
The more context you can provide the better in cases like this.
Are you running on a VM? what's the specs of the box?
Is this a clone? Did you change the hosts file after weblogic installation?
Any SSL configurations?
I know that I just got through dealing with a slow managed server startup due to switching the lookback adaptor's alias. The nodemanager didn't like the switch at all.
Nodemanager doesn't play a part in the admin server startup, so that's probably not your specific issue. But, small changes can affect WLS!