Restrictions on Changing Log File Directories

(Doc ID 1349393.1)

Last updated on OCTOBER 21, 2011

Applies to:

Oracle SOA Platform - Version: 11.1.1.4.0 to 11.1.1.5.0 - Release: 11gR1 to 11gR1
Information in this document applies to any platform.

Symptoms

Do not change the location of log directories unless absolutely necessary. If an absolute path for the log directory is specified, and not a relative path, composite deployment fails.

For example:
After changing the "Log file name" for a SOA managed server in the WLS Console using an absolute path (eg. "/logs/<soa>.log"), any further composite deployment fails with the following error:

Deploying ..failed!
There was an error deploying the composite .....:
Error occurred during deployment of component: ...
to service engine:.. for composite: ....
ORABPEL-01010
Process Generation Failed.
Failed to generate the BPEL process file ...
Could not generate named BPEL process file. The exception reported was ...
deploy.lock (No such file or directory)"

Cause

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