Missing EAR File On Startup Of ALSB / OSB Server Causes Admin Mode Status

(Doc ID 1101675.1)

Last updated on MAY 10, 2017

Applies to:

Oracle Service Bus - Version 3.0 to 10.3.1 [Release Aqualogic Service Bus to AS10gR3]
Oracle Service Bus - Version to [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 12-May-2017***


On an ALSB / OSB domain, when managed servers are restarted they go into Admin state. They can be resumed and then they go into Running state with no problem. No incorrect behavior appears after servers are put into running state.

There is a log message in the startup log for 11g:

java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "0". Underlying error is: "[DeploymentService:290065]Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "0" from server "Server1". Exception is: "Invalid source path : \u01\Middleware\user_projects\domains\Services_ESB1\alsb\config\plan\Plan-ProxyService_-574557.ear"."

In 12c the message will look something like this:

<May 3, 2017, 10:39:27,905 PM UTC> <Error> <Deployer> <BEA-149205> <Failed to initialize the application "SB_JMS_Proxy_N5870bec5.1a595a8e.1.15badc4d9d3.N8000" due to error weblogic.management.DeploymentException: Exception occured while downloading files
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:50)


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