Hello Experts,
We are facing issue related to Foundation Services for which the Managed server in WebLogic going into "ADMIN" state. Below are the logs we found in FoundationServices0.log :
<BEA-149205> <Failed to initialize the application 'staticcontent [Version=11.1.2.2]' due to error weblogic.management.DeploymentException: [J2EE:160177]The application at "/opt/app/Oracle/Middleware/EPMSystem11R1/common/epmstatic" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation..
weblogic.management.DeploymentException: [J2EE:160177]The application at "/opt/app/Oracle/Middleware/EPMSystem11R1/common/epmstatic" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.
at weblogic.application.internal.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:106)
at weblogic.deploy.internal.targetserver.BasicDeployment.createDeployment(BasicDeployment.java:149)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:114)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Jul 24, 2014 4:59:07 PM EDT> <Emergency> <Deployer> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235547373> <BEA-149259> <Server 'FoundationServices0' in cluster 'FoundationServices' is being brought up in administration state due to failed deployments.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548170> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548368> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548374> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548383> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548392> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebService> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548396> <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.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <WebLogicServer> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548401> <BEA-000256> <Invoking weblogic.transaction.internal.StartupClass.main(null)>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <Deployer> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548450> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server FoundationServices0.>
####<Jul 24, 2014 4:59:08 PM EDT> <Info> <Deployer> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235548450> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server FoundationServices0.>
####<Jul 24, 2014 4:59:09 PM EDT> <Info> <Deployer> <ldcae108a> <FoundationServices0> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KTeApvDDWb^ppSw0yY1JoNE8000001> <1406235549582> <BEA-149059> <Module /inspection.wsil of application wsil-wls is transitioning from STATE_PREPARED to STATE_ADMIN on server FoundationServices0.>
Note : Database is Up & Running and we able to connect from SQL client.
Its configured on Red hat linux 5.
Thanks in advance,
Santy.