WebLogic Admin Server Start Up hangs at ‘Log Management’ BEA-170019 IIOP subsystem enabled
I earlier discussed about WebLogic Server startup hanging at “Initializing self-tuning thread pool”, in today’s post I covers fix for WebLogic Server hang but this time while writing ‘Log File‘ and ‘IIOP subsystem enabled‘ in Server logs.
I verified disk space (not 100%), enogh space in /tmp and O.S. user was able to write to /tmp.
Start-up Logs in webLogic Server hangs at
____
<15-Jan-2014 15:11:27 o’clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> <15-Jan-2014 15:11:27 o’clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> <15-Jan-2014 15:11:28 o’clock GMT> <Notice> <Log Management> <BEA-170019> <The server log file /u01/ app/ oracle/ admin/ dev_domain/ aserver/ dev_domain/ servers/ AdminServer/ logs/ AdminServer.log is opened. All server side log events will be written to this file.>
_______
In AdminServer.log
_______
####<15-Jan-2014 15:11:28 o’clock GMT> <Info> <Socket> <testMachine> <AdminServer> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1389798688594> <BEA-000446> <Native IO Enabled.> ####
<15-Jan-2014 15:11:28 o’clock GMT> <Info> <IIOP> <testMachine> <AdminServer> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1389798688861> <BEA-002014> <IIOP subsystem enabled.>
_____________
- Based on feedback from various forums and blog posts, this issue could be because of corrupt LDAP data (WebLogic’s embedded LDAP server).
- Embedded LDAP files in WebLogic are stored at $DOMAIN_HOME/servers/[ServerName]/data/ldap
Fix: Move ldap directory from $DOMAIN_HOME/servers/[ServerName]/data/ and try again .