My Oracle Support Banner

Exception java.lang.IllegalArgumentException: No such file or directory When Altering DBAdapter (Doc ID 1427282.1)

Last updated on JULY 26, 2018

Applies to:

Oracle Service Bus - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Goal

The exception "java.lang.IllegalArgumentException: /opt/web/wl/osb11.1.1.5/osb11/soa/connectors/Plan.xml (No such file or directory)" for the Deployment Plan XML file is given when trying to make changes to the installed DBAdapter.

Example of steps being executed:
1 - Click on Deployments on the left side of the WLS Console Home Page.
2 - Scroll down to DBAdapter. Click on DBAdapter.
3 - Create New Connection Factory.
      a. Click on Configuration tab, followed by Outbound Connection Pools tab
      b. Select javax.resource.cci.ConnectionFactory and Click New.
4 - Select javax.resource.cci.ConnectionFactory and click Next.
5 - Specify the JNDI Name. Next, click Finish.
6 - On the Deployment Plan generation screen, accept the default and click Ok.
7 - Activate Changes.  (The error is seen after clicking Active Changes.)

Stack trace:

weblogic.management.DeploymentException: java.lang.IllegalArgumentException: /opt/web/wl/osb11.1.1.5/osb11/soa/connectors/Plan.xml (No such file or directory)
at weblogic.deploy.internal.targetserver.AppDeployment.parsePlan(AppDeployment.java:205)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.initializeDeploymentPlan(ActivateOperation.java:227)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:204)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Caused By: java.io.FileNotFoundException: /opt/web/wl/osb11.1.1.5/osb11/soa/connectors/Plan.xml (No such file or directory)


The error does NOT occur if the Plan.xml file is copied from the machine that hosts the Admin server to the machine hosting one of the Managed Servers in the Cluster, even though the "Current Location" field specified in the Plan generation screen shows the correct hostname.

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.