SOA Servers Goes To Admin Mode Due To Missing plan.xml File For Adapter - ""

(Doc ID 2253089.1)

Last updated on APRIL 13, 2017

Applies to:

SOA Suite Cloud Service - Version N/A and later
Information in this document applies to any platform.


SOA Server is coming to admin state due to failed deployments. Logs shows the below Errors. java.lang.IllegalArgumentException: /u01/app/oracle/middleware/soa/soa/connectors/Plan.xml (No such file or directory)
at weblogic.deploy.internal.targetserver.AppDeployment.parsePlan(
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(
Truncated. see log file for complete stacktrace
Caused By: /u01/app/oracle/middleware/soa/soa/connectors/Plan.xml (No such file or directory)
at Method)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getInputStream(
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(
Truncated. see log file for complete stacktrace

<Server "CSSOA_server_2" in cluster "CSSOA_cluster" is being brought up in administration state due to failed deployments.>


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms