Thursday, December 16, 2010

ORABPEL-01010 and "Could not generate named BPEL process file" when deploying composite using Ant


When using Ant to deploy a SOA Suite 11g composite project, we received the following error below:
[deployComposite] setting user/password..., user=weblogic
[deployComposite] Processing sar=/home/oracle/scripts/deploy/svn/AhmedHelloWorld2/deploy/sca_AhmedHelloWorld2_rev1.0.jar
[deployComposite] Adding sar file - /home/oracle/scripts/deploy/svn/AhmedHelloWorld2/deploy/sca_AhmedHelloWorld2_rev1.0.jar
[deployComposite] Creating HTTP connection to host:oradev, port:8001
[deployComposite] Received HTTP response from the server, response code=500
[deployComposite] ---->response code=500, error:Error during deployment: Deployment Failed: Error occurred during deployment of component: AhmedHelloWorld2 to service engine: implementation.bpel, for composite: AhmedHelloWorld2: ORABPEL-01010
[deployComposite] Process Generation Failed.
[deployComposite] failure to generate the BPEL process file "".
[deployComposite] Could not generate named BPEL process file. The exception reported was "/u01/app/oracle/middleware/user_projects/domains/soa_domain/deployed-composites/AhmedHelloWorld2_rev1.0/sca_AhmedHelloWorld2_rev1.0/soa_e8794269-88b4-4504-98c4-ea363cb70ad7/SCA-INF/bpel/AhmedHelloWorld2/deploy.lock (No such file or directory)".
[deployComposite] Ensure that the file "" is a valid file to be generated.
[deployComposite] .

Based on another forum posting, it was suggested to check and increase the number of open files.
oracle@oradev> ulimit -n
In my case, it was set a tad low, so I increased it by running "ulimit -n 2048", but that did not resolve my issue.


1. Check your disk space. In our case, our disk was 100% full.

2. Make more space, bounce the "soa_server1", and try again.

Applicable Versions:
  • Oracle SOA Suite 11g (11.1.1.x)
  • Red Hat Linux 5.5


Anonymous said...

I have exactly the same error but we have no problems with the disk space. Have you encountered this issue in other conditions ?

Ahmed Aboulnaga said...

Try checking the /tmp/out.err file immediately after you run Ant. It sometimes provides more information than what is displayed on standard out.