2016-09-20 88 views
0

我正在尋找在Web邏輯上建立羣集服務器。我走了以下步驟,但當我重新啓動我的服務器,然後啓動集羣我得到一個異常。下面列出了例外情況。Weblogic服務器羣集安裝程序11g - 設置服務器實例和羣集

下面是我通過控制檯上的網絡邏輯

Create Cluster 

In the console page mydomain.com/7002/console on the left side 
I click on 

    Environment 

to expand the tree and then click on 

Clusters 

It changes screens on the right. I fill out the data for the 

CLUSTER NAME 

and I left the messaging mode to Uni-Cast 

The multicast address and port are already filled out but are greyed out. 

I then click OK. 

After this I configure the server. On the side on the console page I click on Servers 

Server Config 


I fill out the Server Name: MyServer 

I punch in the Server Listen Address 

Port is defaulted to 7001 which is available 

I then fill out the question 

Should this server belong to a cluster 

I answer 

Yes, Make this a server a member of an existing cluster and I select the cluster I just created. 

I then click Finish 

後,我接受更改並重新啓動服務器的步驟,當我啓動服務器的情況下,我得到了下面的異常的錯誤日誌。任何幫助將不勝感激。

####<Sep 20, 2016 1:57:25 PM CDT> <Debug> <ServerLifeCycle> <DIFDX> <WLS_RUN_MANAGER> <main> <<WLS Kernel>> <> <> <1474397845602> <BEA-000000> <calling halt on w[email protected]> 
####<Sep 20, 2016 1:57:25 PM CDT> <Debug> <DiagnosticContext> <> <> <weblogic.timers.TimerThread> <> <> <> <1474397845604> <BEA-000000> <Invoked DCM.initialValue() for thread id=15, name=weblogic.timers.TimerThread 
java.lang.Exception 
    at weblogic.diagnostics.context.DiagnosticContextManager$1.initialValue(DiagnosticContextManager.java:267) 
    at weblogic.kernel.ResettableThreadLocal.initialValue(ResettableThreadLocal.java:117) 
    at weblogic.kernel.ResettableThreadLocal$ThreadStorage.get(ResettableThreadLocal.java:204) 
    at weblogic.kernel.ResettableThreadLocal.get(ResettableThreadLocal.java:74) 
    at weblogic.diagnostics.context.DiagnosticContextManager$WLSDiagnosticContextFactoryImpl.findOrCreateDiagnosticContext(DiagnosticContextManager.java:365) 
    at weblogic.diagnostics.context.DiagnosticContextFactory.findOrCreateDiagnosticContext(DiagnosticContextFactory.java:111) 
    at weblogic.diagnostics.context.DiagnosticContextFactory.findOrCreateDiagnosticContext(DiagnosticContextFactory.java:94) 
    at weblogic.diagnostics.context.DiagnosticContextHelper.getContextId(DiagnosticContextHelper.java:32) 
    at weblogic.logging.LogEntryInitializer.getCurrentDiagnosticContextId(LogEntryInitializer.java:117) 
    at weblogic.logging.LogEntryInitializer.initializeLogEntry(LogEntryInitializer.java:67) 
    at weblogic.logging.WLLogRecord.<init>(WLLogRecord.java:43) 
    at weblogic.logging.WLLogRecord.<init>(WLLogRecord.java:54) 
    at weblogic.logging.WLLogger.normalizeLogRecord(WLLogger.java:64) 
    at weblogic.logging.WLLogger.log(WLLogger.java:35) 
    at weblogic.diagnostics.debug.DebugLogger.log(DebugLogger.java:231) 
    at weblogic.diagnostics.debug.DebugLogger.debug(DebugLogger.java:204) 
    at weblogic.work.SelfTuningDebugLogger.debug(SelfTuningDebugLogger.java:18) 
    at weblogic.work.ServerWorkManagerImpl$1.log(ServerWorkManagerImpl.java:44) 
    at weblogic.work.SelfTuningWorkManagerImpl.debug(SelfTuningWorkManagerImpl.java:597) 
    at weblogic.work.RequestManager.log(RequestManager.java:1204) 
    at weblogic.work.RequestManager.addToCalendarQueue(RequestManager.java:315) 
    at weblogic.work.RequestManager.addToPriorityQueue(RequestManager.java:301) 
    at weblogic.work.RequestManager.executeIt(RequestManager.java:248) 
    at weblogic.work.SelfTuningWorkManagerImpl.scheduleInternal(SelfTuningWorkManagerImpl.java:164) 
    at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:144) 
    at weblogic.timers.internal.TimerManagerFactoryImpl$WorkManagerExecutor.execute(TimerManagerFactoryImpl.java:132) 
    at weblogic.timers.internal.TimerManagerImpl.waitForStop(TimerManagerImpl.java:241) 
    at weblogic.timers.internal.TimerManagerImpl.stop(TimerManagerImpl.java:98) 
    at weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:250) 
+0

您確定管理服務器實例的IP /端口與MyServer的IP /端口之間沒有衝突嗎? – slwk

+0

找到我的解決方案。它最終成爲超時問題。服務器花了很長時間才發現該實例沒有迴應,因此假設它無法通過。一旦我將超時時間延長了一段時間,它終於完成並工作了。 – Dale

回答

0

解決方案:它最終成爲超時問題。服務器花了很長時間才發現該實例沒有迴應,因此假設它無法通過。一旦我將超時時間延長了一段時間,它終於完成並工作了。