This discussion is archived
4 Replies Latest reply: Feb 20, 2013 12:53 PM by the_assface RSS

Admin Status - Server Startup

the_assface Explorer
Currently Being Moderated
I have a WLP 10.3 environment that has been working well but all of the sudden I am starting to get a few JVM's that go into 'ADMIN' status rather than 'RUNNING' after I restart them. Most of the times a simple 'resume' will fix it but I need to have them go into running after reboots, etc.. The logs show no reason for this behavior. Any ideas?

Thanks
  • 1. Re: Admin Status - Server Startup
    Peter.Lorenzen Explorer
    Currently Being Moderated
    Hi,

    You must have some module with a problem: Application, Lib, JMS, Data Source etc.

    See:
    http://middlewaremagic.com/weblogic/?p=6407

    Regards Peter
  • 2. Re: Admin Status - Server Startup
    the_assface Explorer
    Currently Being Moderated
    Thanks for the suggestion and link. However, in this case the server going into ADMIN is the adminserver itself. In our case, the adminserver has nothing deployed to it, no data sources, JMS, etc....it is merely the adminserver which has never had any changes to it.
  • 3. Re: Admin Status - Server Startup
    the_assface Explorer
    Currently Being Moderated
    Okay, finally found a smoking gun here. But still not sure why it's an issue....I am getting the error below in the AdminServer.log and it is from a diagnostic module I setup. The diag module is targeted to some of the managed servers but not the admin server. However, I assume that the adminServer is involved and having what apparently is a JNDI issue with the mail session named, "WLMail". I have this same exact setup in my production environment and it's admin log does not have errors and does not start the AdminServer n ADMIN mode like this test environment does....any ideas?


    ####<Feb 20, 2013 1:02:39 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386959387> <BEA-320114> <Initializing the Diagnostics Harvester.>
    ####<Feb 20, 2013 1:02:39 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386959403> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Feb 20, 2013 1:02:39 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386959403> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Feb 20, 2013 1:02:39 PM CST> <Error> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386959403> <BEA-320052> <Error occurred while initializing a SMTP notification:
    javax.naming.NameNotFoundException: Unable to resolve 'WLMail'. Resolved ''; remaining name 'WLMail'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         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)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.diagnostics.watch.SMTPNotificationListener.initializeSMTP(SMTPNotificationListener.java:307)
         at weblogic.diagnostics.watch.SMTPNotificationListener.<init>(SMTPNotificationListener.java:119)
         at weblogic.diagnostics.watch.WatchSubModule.identifySMTPNotifications(WatchSubModule.java:354)
         at weblogic.diagnostics.watch.WatchSubModule.identifyNotifications(WatchSubModule.java:94)
         at weblogic.diagnostics.watch.WatchSubModule.initializeFromConfiguration(WatchSubModule.java:433)
         at weblogic.diagnostics.watch.WatchSubModule.activate(WatchSubModule.java:477)
         at weblogic.diagnostics.module.SubModuleRegistry$ModuleInstance.activate(SubModuleRegistry.java:189)
         at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:287)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Feb 20, 2013 1:02:39 PM CST> <Error> <Deployer> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386959418> <BEA-149231> <Unable to set the activation state to true for the application 'CommandNet Start'.
    weblogic.application.FatalModuleException:
         at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:293)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Caused By: javax.naming.NameNotFoundException: Unable to resolve 'WLMail'. Resolved ''; remaining name 'WLMail'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         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)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.diagnostics.watch.SMTPNotificationListener.initializeSMTP(SMTPNotificationListener.java:307)
         at weblogic.diagnostics.watch.SMTPNotificationListener.<init>(SMTPNotificationListener.java:119)
         at weblogic.diagnostics.watch.WatchSubModule.identifySMTPNotifications(WatchSubModule.java:354)
         at weblogic.diagnostics.watch.WatchSubModule.identifyNotifications(WatchSubModule.java:94)
         at weblogic.diagnostics.watch.WatchSubModule.initializeFromConfiguration(WatchSubModule.java:433)
         at weblogic.diagnostics.watch.WatchSubModule.activate(WatchSubModule.java:477)
         at weblogic.diagnostics.module.SubModuleRegistry$ModuleInstance.activate(SubModuleRegistry.java:189)
         at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:287)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960027> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960183> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960183> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseService for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960198> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Jms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960214> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12 for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <WebService> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960214> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceSoap12Https for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
    ####<Feb 20, 2013 1:02:40 PM CST> <Info> <netuix> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386960510> <BEA-423101> <[console] Initializing the NetUIx container>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <netuix> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961025> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [console//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <netuix> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961399> <BEA-423101> <[consolehelp] Initializing the NetUIx container>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <netuix> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961462> <BEA-423120> <WEB-INF/client-classifications.xml file not found at uri [consolehelp//WEB-INF/client-classifications.xml]. Classifications functionality not enabled.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961571> <BEA-090840> <Registered SAML service samlacs at URI /acs in application context /samlacs.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961571> <BEA-090840> <Registered SAML service samlars at URI /ars in application context /samlars.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its in application context /samlits_ba.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its/post in application context /samlits_ba.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its/artifact in application context /samlits_ba.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its in application context /samlits_cc.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its/post in application context /samlits_cc.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1361386961586> <BEA-090840> <Registered SAML service samlits at URI /its/artifact in application context /samlits_cc.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961586> <BEA-320000> <The Diagnostics subsystem is initializing on Server AdminServer.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Log Management> <qaportal1> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961649> <BEA-170025> <Initialized Domain Logging. Domain log events will be written to C:\Oracle\Middleware\user_projects\domains\QA11\servers\AdminServer\logs/QA11.log.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961711> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Notice> <Log Management> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961742> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961742> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Diagnostics> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961742> <BEA-320119> <The Harvester is now in a inactive state.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961758> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Notice> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961758> <BEA-002613> <Channel "Default" is now listening on 10.5.110.227:8098 for protocols iiop, t3, ldap, snmp, http.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Notice> <WebLogicServer> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961758> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "QA11" running in Production Mode>
    ####<Feb 20, 2013 1:02:41 PM CST> <Notice> <WebLogicServer> <qaportal1> <AdminServer> <main> <<WLS Kernel>> <> <> <1361386961774> <BEA-000365> <Server state changed to ADMIN>
    ####<Feb 20, 2013 1:02:41 PM CST> <Notice> <WebLogicServer> <qaportal1> <AdminServer> <main> <<WLS Kernel>> <> <> <1361386961774> <BEA-000360> <Server started in ADMIN mode>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961836> <BEA-002635> <The server "PortalServer2" connected to this server.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961852> <BEA-002635> <The server "WebProxyServer2" connected to this server.>
    ####<Feb 20, 2013 1:02:41 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386961961> <BEA-002635> <The server "FPCE2" connected to this server.>
    ####<Feb 20, 2013 1:02:42 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386962086> <BEA-002635> <The server "CommandNet1" connected to this server.>
    ####<Feb 20, 2013 1:02:42 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386962117> <BEA-002635> <The server "CommandNet2" connected to this server.>
    ####<Feb 20, 2013 1:02:42 PM CST> <Info> <Server> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361386962273> <BEA-002635> <The server "FPCE1" connected to this server.>
  • 4. Re: Admin Status - Server Startup
    the_assface Explorer
    Currently Being Moderated
    I found the issue. The admin server was not targeted in the mail session, however, one of the diagnostic modules has it targeted. Untargeted it and restarted and the adminserver came up normally. Hope this helps someone in the future.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points