點擊藍字java
關注求勾搭web
前言：Oracle WebLogic中間件在網站部署過程當中常常會使用到。該產品系列的核心是Oracle WebLogic服務器，它是一個功能強大和可擴展的Java EE服務器。今天整理了在運維過程當中常常會遇到的各類報錯以及解決方法，純技術乾貨，但願可以對正在學習weblogic過程當中的您提供幫助。spring
weblogic有兩種部署方式，單點模式和集羣模式，單點模式直接建立一個域，在控制檯進行程序部署便可；而集羣模式分爲admin（管理）節點和Managed（被管理）節點，管理節點經過控制檯對被管節點進行管理，程序部署在被管節點的集羣上。不管是單點模式，仍是集羣模式，常見的報錯基本一致。數據庫
基本概念
緩存
Domain ：ruby
域是做爲單元進行管理的一組相關的 WebLogic Server 資源。一個域包含一個或多個 WebLogic Server 實例，這些實例能夠是集羣實例、非羣集實例，或者是集羣與非羣集實例的組合。一個域能夠包含多個集羣。域還包含部署在域中的應用程序組件、此域中的這些應用程序組件和服務器實例所需的資源和服務。應用程序和服務器實例使用的資源和服務示例包括計算機定義、可選網絡通道、鏈接器和啓動類。bash
Domain 中包含一個特殊的 WebLogic 服務器實例，叫作 Administration Server，這是咱們配置管理Domain中全部資源的核心。一般，咱們稱加入Domain中的其餘實例爲 Managed Server，全部的Web應用、EJB、Web Services和其餘資源都部署在這些服務器上。服務器
Administration Server ：微信
管理服務器是控制整個域配置的中心操做節點，管理服務器維護着整個域 的配置並將配置分配到每一個被管理服務器 Managed Server 中。咱們能夠經過三個渠道訪問管理服務器：Admin Server console、Oracle WebLogic Scripting Tool WLST、JMX客戶端（經過WebLogic提供的API來實現），最後咱們還能夠經過SNMP協議來監控Admin Server的狀態。網絡
Managed Server ：
被管理服務器是一個WebLogic Server的實例，他從Admin Server那裏獲取配置信息。一般在Managed Server上部署本身的服務、組件或應用。基於性能考慮，Managed Server維護着一份只讀的域配置文件，當服務啓動的時候，會從Admin Server上同步配置文件信息，若是配置文件發生了改變，Admin Server也會將改變推送到Managed Server上。
下面咱們看看常見的weblogic報錯，weblogic的日誌中，咱們能夠經過BEA開頭的報錯code進行問題查找。
經過nohup ./startWebLogic.sh &命令啓動管理節點後，tail -f nohup.out查看日東日誌，發現日誌上存在BEA-000386報錯，具體日誌以下：
<2019-10-12 下午05時22分21秒 CST> <Notice> <WebLogicServer> <BEA-0OO365> <Server state changed to STARTING><2019-10-12 下午05時22分21秒 CST> <Info> <WorkManager> <BEA-002900> initializing self-tuning thread poo1><2019-10-12 下午05時22分21秒 CST> <Notice> <Log Management <BEA-170019> <The server log file /weblogic/user_projects/domains/admindoiiiain/servers/AdminServer/logs/AdminServer.log is opened. All ;erver side log events will be written to this file.><2019-10-12 下午05時22分22秒 CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.<Notice> <Log Management <BEA-170019> <The server log file java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:38) at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:33) at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:154) at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:61) at weblogic.server.channels.ChannelService.start(ChannelService.java:207) Truncated. see log file for complete stacktraceCaused By: java.net.UnknownHostException: weblogic1: weblogic1 at java.net.InetAddress.getLocalHost(InetAddress.java:1360) at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:36) at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:33) at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:154) at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:61) Truncated. see log file for complete stacktrace><2019-10-12 下午05時22分22秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED><2019-10-12 下午05時22分22秒 CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
日誌上有一個描述很重要，Could not obtain the localhost address，經過查閱資料，發現是因爲/etc/hosts沒有配置本機服務地址致使出現此錯誤。
原始配置：
[root@weblogic1 ~]# cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
增長主機名和eth0對應關係，修改以下：
[root@weblogic1 ~]# cat /etc/hosts127.0.0.1 localhost 192.168.101.2 weblogic1::1 localhost
再次重啓管理節點，正常啓動
使用命令nohup ./startManagedWebLogic.sh webserver01 http://10.199.132.12:8801 &啓動被管節點，webserver01 爲被管節點服務名，出現BEA-141196報錯。
.security.allowCryptoJDefaultPRNG=true><Dec 8, 2018 3:55:38 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "1,544,313,339,787". Underlying error is: "null" at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86) at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:165) at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:75) at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56) at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentReceiverService.java:920) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentReceiverService.java:879) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAccessDeploymentReceiverService.java:728) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymentReceiverService.java:699) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverService.java:169) at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:462) at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:167) at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:883) at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:570) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:471) at weblogic.Server.main(Server.java:71)<Dec 8, 2018 3:55:40 PM PST> <Error> <Management> <BEA-141196> <The managed server could not update the configuration files during the registration with the deployment service. The update failed due to an exception:weblogic.management.DeploymentException: Exception occured while downloading files at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doDownload(ConfigDataUpdate.java:83) at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56) at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.downloadFiles(RuntimeAccessDeploymentReceiverService.java:920)
解決方法：
從日誌Exception occured while downloading files能夠看出，被管節點從管理節點同步配置文件時出現異常，參照網上資料將管理節點目錄/Oracle/Middleware/user_projects/domains/admindomain/security/SerializedSystemIni.dat的文件拷貝到受控服務器security對應目錄下，再次重啓，被管節點正常啓動。
weblogic的啓動內存參數若是沒有設置，會使用默認的內存參數啓動，咱們能夠經過調整啓動內存參數解決此問題。編輯/Oracle/Middleware/user_projects/domains/webdomain01/bin/startWebLogic.sh文件，增長以下內存參數
export USER_MEM_ARGS="-server -d64 -Xmx2048m -Xms2048m -XX:PermSize=256m -XX:+UseParallelGC -XX:ParallelGCThreads=12 -XX:+UseParallelOldGC -XX:+UseParallelOldGC -XX:ReservedCodeCacheSize=128m -XX:+HeapDumpOnOutOfMemoryError -Xloggc:./logs/$SERVER_NAME/$SERVER_NAME.gc.$$.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Djava.security.egd=file:/dev/./urandom -XX:ErrorFile=./logs/java_error$$.log"
-XX:PermSize參數調大後問題解決。
weblogic控制檯上集羣狀態顯示爲admin狀態，正常狀況下應該爲running
<Dec 10. 2018 6:24:17 P11 PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY><Dec 10. 2018 6:24:17 P11 PSi> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING><Dec 10. 2018 6:24:25 P11 PSi> <Error> <Deployer> .c8EA-149205> <Failed to initialize the application jdbc/ZBDataSource due to error weblogic.application.ModuLeException: .weblogic.application.ModuleException: at weblogic.jdbc.module.)DocNodule.prepare(J080lodule.java:327) at weblogic.application,internal,flow. ModuleListenerlnvoker. p repa reOloduleListenerlnvoker. java: 199) at weblogic.application.internal.flow.DeployinentCallbackFlow$1.next(DeployuientCallbackFl.ow. java :517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineOriver.java:52) Truncated. see log file for complete stacktraceCaused By: weblogic.common.ResourceException: weblogic.comion.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:ORA-12505. TNS:listener does not currently know of SID given in connect descriptorat weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:285)at weblogic.co.mon. resourcepool.ResourcePoollmpl.makeResources(ResourcePoollmpl.java:1323)at weblogic.coion. resourcepool.ResourcePoolImp1..iiakeesources(ResourcePoolImpl.java:1240)at weblogic . coion. resourcepool .ResourcePoollmpl . start(ResourcePoolliipl .java :251)at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1329)Truncated. see log file for complete stacktrace<Dec 10. 2018 6:24:25 P11 PSI> <Emergency> <DepLoyer> ‘c8EA.149259> <Server sbfwebserverer in cluster •cluster_web is being brought up in aiinistration state due to failed deployments.><Dec 10. 2018 6:24:26 PM PSi> <Notice> <Log Management> <8EA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.><Dec 10. 2018 6:24:26 P11 PST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging><Dec 10. 2018 6:24:26 P11 PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of cluster_web.><Dec 10. 2918 6:24:56 PM PST> <Notice> <Server> <BEA-902613> <Channel Default’ is now listening on 192.168.191.2:8811 for protocols iiop. t3. CLLJSTER-BI)ADCAST. idap. srnp. http.><Dec 10. 2018 6:24:56 P11 PSi> <Notice> <WebLogicServer> <8EA-000330> <Started WebLogic Managed Server webserver0l for domain admindamain running in Production Mode><Dec 10. 2018 6:24:57 P11 PSi> <Notice> <WebLogicServer> <8EA-000365> <Server state changed to ADMIN><Dec 10. 2018 6:24:57 P11 PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
weblogic控制檯上顯示服務器爲admin，從日誌上也能夠看到initialize the application jdbc/ZBDataSource數據源初始化失敗，控制檯配置的數據源沒法鏈接致使，數據庫問題解決後，域正常啓動。
控制檯建立持久化存儲後，啓動被管節點出現以下報錯。
<Dec 11. 2018 1:19:38 AM PST> <Notice> <Log Management> <8EA-170019> <The server log file /weblogic/useryrojects/domains/webdomain02/servers/webservero2/Logs/webserver02.log is opened All, server side log events will be written to this file.> <Dec 11. 2018 1:19:39 AM PST> <Emergency> <Store> <BEA-280060> <The persistent store LSDIAGNOSTICS encountered a fatal, error, and it must be shut down: weblogØ ., CException: [Store:2801051The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS0OO0O0.DAT. - weblogic . store. PersistentSto reFatalException: [Sto re: 280105] The persistent file store ..S_DIAGNOSTICS cannot open file — at weblogic .store.io .file.FileStorelO.open(FileStorelO.java :128)at weblogic.store.internal .PersistentStorelmpl.. recoverStoreConnections(PersistentStorelmpL.java :435)at weblogic.store.interrial.PersistentStorelmpl.open(PersistentStorelmpl.java:423)at weblogic.store.xa.PersistentStoreManagerXA.createfileStore(PersistentStorelianagerXA.java:117)at webtogic .diagnostics .archive.DiagnosticSto reRepository.getStore(DiagnosticStoreRepository. java :91)Truncated. see log file for complete stacktraceCaused By: java.io.IoException: Error from fcntl() for file locking Resource temporarily unavailable. errno=11at weblogic.store.io.file.direct.DirectloNative.openconsiderLock(Native Method)at weblogic.store.io.file.direct.DirectFileChannel.<init>(DirectFilechannel.java:54)at weblogic.store.io.file.direct.DirectlOl4anager.open(DirectlOl4anager.java:179)at weblogic.store.io.fiLe.StoreFite.openlnternal(StoreFite.java:138)at weblogic.store.io.fiLe.StoreFile.open(StoreFile.java:161)Truncated. see log file for complete stacktraceNo matching store mbean found for =WLS_DIA1OSTICS. must be a default store.<Dec 11. 2018 1:19:39 NI PST> <Critical> <WebLogicServer> <SEA-000362> <Server failed. ReasonThere are 1 nested errors:weblogic . diagnostics .lifecycle.DiagnosticCo.ponentLifecycteException: weblogic . sto re.PersistentSto refatatException: [Store: 2801051The persistent file store LS_DIAGNOSTIcS cannot open file b&S_DIAGNOSTICS000000.DAT.at webtogic .diagnostics.lifecycle.ArchiveLifecyclelmpl . initialize(ArchiveLifecyclelmpl java :97)at weblogic.diagnostics.lifecycLe.DiagnosticFoundationService.start(DiagnosticFoundationService.java :108)at weblogic .t3.srvr .SubsysteiiRequest. run(SubsystemRequest .java :64)at weblogic.work.Executemread.execute(ExecuteThread.java:263)at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)Caused by: weblogic.store.PersistentStoreFataLException: [Store:2801051The persistent file store t.S_DIAGNOSTICS cannot open file WLS_DIAGNOSTICS0OOOOO.DAT.
解決辦法：找到WLS_DIAGNOSTICS000000.DAT這個文件，刪除後再啓動weblogic。
[weblogic@weblogic2 weblogic]$ find ./ -name WLS_DIAGNOSTICSOOOOOO.DAT...[weblogic@weblogic2 weblogic]$ rm ./user_projects/domains/webdomain01/servers/webserver02/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
此問題的根源是被管節點的重啓腳本中沒有刪除緩存致使。
/oracle/Middleware/user_projects/domains/webdomain01/servers/webserver01目錄下cache，data，stage和tmp目錄須要刪除。
這個報錯常常出如今程序war包部署和升級重啓時發生報錯，具體報錯以下：
<Jun 8, 2020 8:42:35 PM CST> <Warning> <HTTP> <BEA-101162> <User defined listener com.oracle.weblogic.wsee.wrapper.org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'testConnectionFactory' defined in URL [zip:/weblogic/user_projects/domains/webdomain01/servers/webserver01/tmp/_WL_user/test-service-web-ear/nzlkck/war/WEB-INF/lib/test-service-size-web-1.0.014-SNAPSHOT.jar!/spring/jms/lhjydzfk-jms-context.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved ''; remaining name 'jms/testConnectionFactory'.org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'testConnectionFactory' defined in URL [zip:/weblogic/user_projects/domains/webdomain01/servers/webserver01/tmp/_WL_user/test-service-web-ear/nzlkck/war/WEB-INF/lib/test-service-size-web-1.0.014-SNAPSHOT.jar!/spring/jms/lhjydzfk-jms-context.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved ''; remaining name 'jms/testConnectionFactory' at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1628) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) Truncated. see log file for complete stacktraceCaused By: javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved ''; remaining name 'jms/testConnectionFactory' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1148) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:253) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) Truncated. see log file for complete stacktrace> <Jun 8, 2020 8:42:35 PM CST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'test-service-web-ear'.weblogic.application.ModuleException: at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1531) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:488) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) Truncated. see log file for complete stacktraceCaused By: javax.naming.NameNotFoundException: While trying to lookup 'jms.testConnectionFactory' didn't find subcontext 'jms'. Resolved ''; remaining name 'jms/testConnectionFactory'
出現上面報錯，從日誌上看是ConnectionFactory不能解析，致使程序包沒法active.
主要分下面三種狀況
weblogic控制檯建立的鏈接工廠名字錯誤，程序包調用時沒法識別；
鏈接工廠建立後，沒有指定目標服務器，或者少指定目標節點；
重啓節點沒有清理緩存。
密碼問題也是weblogic啓動過程當中出現機率較多的問題，管理節點重啓出現以下報錯
nohup ./startWebLogic.sh &
<Apr 16, 2019 2:50:46 PM CST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.> <Apr 16, 2019 2:50:46 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:960)at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:888)at weblogic.security.SecurityService.start(SecurityService.java:141)at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)Truncated. see log file for complete stacktraceCaused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic deniedat weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)at java.security.AccessController.doPrivileged(Native Method)at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)Truncated. see log file for complete stacktrace> <Apr 16, 2019 2:50:46 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED> <Apr 16, 2019 2:50:46 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
首先多是密碼文件發生變更，按照常規方法解決，修改/oracle/Middleware/user_projects/domains/admindomain/servers/AdminServer/security目錄下boot.properties文件（修改前記得請備份），重啓驗證。
若是重啓後boot.properties文件中密碼仍是明文，則證實密碼文件DefaultAuthenticatorInit.ldift沒法對boot文件加密，採用重置密碼方式解決，步驟以下。
備份文件
cd /oracle/Middleware/user_projects/domains/admindomainmv DefaultAuthenticatorInit.ldift DefaultAuthenticatorInit.ldift-bak
從新生成DefaultAuthenticatorInit.ldift文件
java -cp /oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar weblogic.security.utils.AdminAccount weblogic ceshi2015 .（注：空格後加逗號）
[weblogic@weblogic1 security]$ java -cp /oracle/Middleware//wlserver_10.3/server/lib/weblogic.jar weblogic.security.utils.AdminAccount weblogic ceshi2015 .
[weblogic@weblgoic1 security]$ lltotal 40-rw-rw-r-- 1 weblogic weblogic 3301 Sep 12 2019 DefaultAuthenticatorInit.ldift-rw-rw-r-- 1 weblogic weblogic 3301 Aug 27 2019 DefaultAuthenticatorInit.ldift.bak-rw-r----- 1 weblogic weblogic 2398 Mar 4 2019 DefaultRoleMapperInit.ldift-rw-r----- 1 weblogic weblogic 64 Mar 4 2019 SerializedSystemIni.dat-rw-r----- 1 weblogic weblogic 22654 Mar 4 2019 XACMLRoleMapperInit.ldift
再次刪除緩存重啓成功，被管節點能夠經過拷貝管理節點DefaultAuthenticatorInit.ldift文件到被管進行處理。
總結：上述報錯類型概括了weblogic運維過程總常見的問題，實際工做過程當中，能夠經過在重啓腳本中設置刪除緩存命令，避免出現沒必要要的運維問題。通常報錯能夠經過BEA-xxx進行搜索。
往期精選
July 2020
文字：原創
掃描二維碼
關注咱們
微信公衆號 : 運維之美
你「在看」我嗎？
本文分享自微信公衆號 - 運維之美（ywzm8976）。
若有侵權，請聯繫 support@oschina.cn 刪除。
本文參與「OSC源創計劃」，歡迎正在閱讀的你也加入，一塊兒分享。