weblogic 停在starting状态的解决办法

http://www.techpaste.com/2013/10/weblogic-admin-server-startup-hanging-coming-running-state/

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. 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. 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.

Solution 1

Usually it used to get stuck at starting with below logs:

weblogic server hangs at startup and used to get stuck at above point and will not even log anything. 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. We saw the server recreated the data folder by itself and started up fine without any hangs.

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, EmbeddedLDAP.delete, EmbeddedLDAP.tran, EmbeddedLDAP.twpos files with the backed up file and restarted the Admin Server. 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.)

http://www.techpaste.com/2013/04/steps-resolve-embeddedldap-error-java-lang-nullpointerexception-weblogic/

 Solution 2

If you are getting below error while starting the managed server try to remove the edit.lok file, it will fix the issue or regenerate the boot.properties file.

    
    
     
  
 Solution 3
 
  
 If you are getting below error before starting the server or just after starting the server and weblogic server not starting then please execute below mentioned steps to fix it.
 
  
 Delete all the corrupted DAT files under /opt/domain/server_name/servers/AdminServer/data/store/diagnostics/*.DAT and try to restart the server again.
 
  
 
    
    
    
  
 
  
####     
 <> <> <> <1161766995356>  
####     <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <
<> <26be653e45def710:-52c11f7a:10e7eb579cc:-7fe1-0000000000000001><1161767249271>  (PersistentStoreDataArchive.java:268)
at weblogic.diagnostics.archive.wlstore.EventsPersistentStoreDataArchive.(EventsPersistentStoreDataArchive.java:53)
at weblogic.diagnostics.accessor.DiagnosticDataAccessServiceFactory.createEventsDataAccessService(DiagnosticDataAccessServiceFactory.java:174)
at weblogic.diagnostics.accessor.DiagnosticDataAccessServiceFactory.createDiagnosticDataAccessService(DiagnosticDataAccessServiceFactory.java:61)
at weblogic.diagnostics.accessor.DiagnosticDataAccessRuntime.createDiagnosticDataAccessService(DiagnosticDataAccessRuntime.java:164)
at weblogic.diagnostics.accessor.DiagnosticDataAccessRuntime.createDiagnosticDataAccessRuntime(DiagnosticDataAccessRuntime.java:100)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime$1.run(DiagnosticAccessRuntime.java:144)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:140)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:94)
at weblogic.diagnostics.instrumentation.EventQueue.getArchive(EventQueue.java:338)
at weblogic.diagnostics.instrumentation.EventQueue.access$200(EventQueue.java:46)
at weblogic.diagnostics.instrumentation.EventQueue$ArchiveEventsAction.run(EventQueue.java:371)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.diagnostics.instrumentation.EventQueue.timerExpired(EventQueue.java:316)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
java.io.IOException: Error reading from file, No such file or directory, errno=2
at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)
at weblogic.store.io.file.StoreFile.read(StoreFile.java:275)
at weblogic.store.io.file.Heap.getNextRecoveryFile(Heap.java:792)
at weblogic.store.io.file.Heap.open(Heap.java:181)
at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:83)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:332)
at weblogic.store.PersistentStoreManager.createFileStore(PersistentStoreManager.java:201)
at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:54)
at weblogic.diagnostics.archive.wlstore.PersistentStoreDataArchive.getArchiveSchema(PersistentStoreDataArchive.java:309)
 
  
 Solution 4
 
  
 If you are getting below error while starting the server and weblogic server not starting then follow below mentioned steps to fix this issue.
 
  
 Note: Always keep backup of files before removing it.
 1: Edit the file, use plain text username and password instead of encrypted like
 Username: weblogic
 password: Weblogic1
 After start the server from command line, it will encrypt again automitically.
 2: Remove the ManagedServerDir/data/ldap directory completely or restore it from the automated backups taken @ /mydomain/WLS/user_projects/domains/wls_mydomain/servers/AdminServer/data/ldap/backup folder.
 3: Now try to start the server from the command prompt and provide the username/password used to login to the Admin Console.
 
  
####     <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1275028553535>  
####     
 <> <> <> <1275028553535>   
  
  
 
  These  are few solutions which we implement to make things work when you have issues like weblogic server not starting or weblogic server hangs at startup . If you have few other solutions which is commonly used by you then please post in comments it will help others to debug there issue.