this time it came up fine, once its up, to avoid this situation again follow steps mentioned here: (i.e: Login to WebLogic console, click on domain name on left pane –> go to security tab –> Embedded LDAP tab –> click on “Refresh replica at startup” option.) So we came to know the issue is with the data folders some file corruption, so we extracted the old backups which gets stored as EmbeddedLDAPBackup.1.zip in /mydomain/WLS/user_projects/domains/wls_mydomain/servers/AdminServer/data/ldap/backup folder and replaced all existing EmbeddedLDAP.data, EmbeddedLDAP.index, lete, an, EmbeddedLDAP.twpos files with the backed up file and restarted the Admin Server. We saw the server recreated the data folder by itself and started up fine without any hangs. After many tries we came to know the issue was with data folder inside /mydomain/WLS/user_projects/domains/wls_mydomain/servers/AdminServer/data folder, so to check if its really issue with data folder we renamed/moved the data folder to data_backup and tried to start it again.
Weblogic server hangs at startup and used to get stuck at above point and will not even log anything. Usually it used to get stuck at starting with below logs: Please follow below solutions and see which one works for your environment for issues like weblogic server not starting or weblogic server hangs at startup. This might come due to many reasons, we use to frequently see these errors on old weblogic setups and finally started keeping record of solutions which we tried to fix them.
While starting weblogic admin server, weblogic server not starting or weblogic server hangs at startup at one point with out any further logs on stdout.
0 kommentar(er)
