_sjz.
This entry was dated Nov 28. May we expect a response anytime soon?
<Server
DGCIdlePeriodsUntilTimeout=10
/>
"Judy" <judy...@pcshs.com> wrote in message
news:3c2b8a15$1...@newsgroups.bea.com...
Should the solution you offered below still apply? I'm not sure exactly what
has to be done. For each server I have a config entry like:
<Server Cluster="OpusCluster" ListenAddress="opus-dev03" Machine="dev03"
Name="OpusServer03">
<KernelDebug Name="OpusServer03" />
<WebServer Name="OpusServer03" />
<ExecuteQueue Name="default" ThreadCount="15" />
<SSL Name="OpusServer03" />
<ServerDebug Name="OpusServer03" />
<ServerStart Name="OpusServer03" />
<Log FileName="OpusServer03.log" Name="OpusServer03" />
</Server>
Do I add the DGCIdlePeriodsUntilTimeout entry somewhere in this section? Is
order important?
Is there any other information on this exception? It appears to be happening
when our network or one of the servers slows down.
Thanks,
Dave
"Zach" <za...@nospam.com> wrote in message
news:3c32...@newsgroups.bea.com...
> <Server Cluster="OpusCluster" ListenAddress="opus-dev03" Machine="dev03"
> Name="OpusServer03" DGCIdlePeriodsUntilTimeout=10>
> <KernelDebug Name="OpusServer03" />
> <WebServer Name="OpusServer03" />
> <ExecuteQueue Name="default" ThreadCount="15" />
> <SSL Name="OpusServer03" />
> <ServerDebug Name="OpusServer03" />
> <ServerStart Name="OpusServer03" />
> <Log FileName="OpusServer03.log" Name="OpusServer03" />
> </Server>
_sjz.
***************************************************************************
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: Error parsing
configur
ation on line 17, column 72
at
weblogic.management.internal.xml.ConfigurationParser.parse(Configurat
ionParser.java:122)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:261)
at
weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy1.loadDomain(Unknown Source)
at
weblogic.management.AdminServer.configureFromRepository(AdminServer.j
ava:188)
at weblogic.management.AdminServer.configure(AdminServer.java:173)
at weblogic.management.Admin.initialize(Admin.java:239)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
***************************************************************************
Line 17, column 72 is the "=" in the expression
"DGCIdlePeriodsUntilTimeout=10".
Dave
"Zach" <za...@nospam.com> wrote in message
news:3c44...@newsgroups.bea.com...
"Tom Barnes" <dev....@not.my.address.com> wrote in message
news:3C45CA17...@not.my.address.com...