Weblogic Server群集设置11g - 设置服务器实例和群集

时间:2016-09-20 19:43:01

标签: java oracle oracle11g weblogic weblogic11g

我希望在Web Logic上设置群集服务器。我走了以下步骤但是当我重新启动服务器然后启动集群时我得到了一个异常。下面列出了例外情况。

以下是我在Web Logic中的控制台上执行的步骤

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 weblogic.nodemanager.NMService@3c3d22af> 
####<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)

1 个答案:

答案 0 :(得分:0)

解决方案:它最终成为超时问题。服务器花了这么长时间才提出实例假设没有回复,因此假设它无法通过。一旦我将超时增加到更长时间,它终于出现并且有效。