Restrictions on Changing Log File Directories
(Doc ID 1349393.1)
Last updated on MARCH 07, 2019
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11gR1]
Information in this document applies to any platform.
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.
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:
There was an error deploying the composite .....:
Error occurred during deployment of component: ...
to service engine:.. for composite: ....
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)"
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