Unable to deploy a BPEL process with rules

Question

Hi All
I created a very simple BPEL process and defined a business Rule in composite, that I call from within my BPEL process.
I am however not able to deploy the project completely successfully.
I am using JDEV 11g to build/deploy my projects on a SOA_Suite_11g. Note that I can deploy a project successfully if it does not have a business rule.
This is what I see in the 'Deployment Log' tab:
[01:49:17 PM] Deploying profile...
[01:49:17 PM] Wrote SAR file to /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Deploying sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
[01:49:17 PM] Processing sar=/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Adding sar file - /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
[01:49:17 PM] Preparing to send HTTP request for deployment
[01:49:17 PM] Creating HTTP connection to host:redunca.pvo.groundhog.com.au, port:8001
[01:49:17 PM] Sending internal deployment descriptor
[01:49:17 PM] Sending archive - sca_FLThree_rev1.0.jar
[01:49:19 PM] Received HTTP response from the server, response code=500
[01:49:19 PM] Error deploying archive sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
[01:49:19 PM] HTTP error code returned [500]
[01:49:19 PM] Error message from server:
Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
Process Generation Failed.
failure to generate the BPEL process file "".
Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
Ensure that the file "" is a valid file to be generated.
: Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
Process Generation Failed.
failure to generate the BPEL process file "".
Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
Ensure that the file "" is a valid file to be generated.
[01:49:19 PM] Check server log for more details.
[01:49:19 PM] #### Deployment incomplete. ####
[01:49:19 PM] Error deploying archive file:/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Any ideas..
Thanks

Answer 1

"Too many open files" issue is most likely because of a (few) Sun JDK6 bug(s). These bugs may not even get fixed in JDK6. It could hit at runtime or compile time depending on the number of jar files getting used and/or a few other variations around the use of file descriptors at a time by the JDK/JRE. One can use "lsof -p <pid>" command on Linux and see how the File Descriptors are growing when this issue is seen. E.g. use the pid of junit java process and not the main Ant java process if you want to debug at runtime. For compile time, grep on the compiler process.
Increasing the limit of file descriptors is used as a workaround.
How to increase per-process per-user file descriptor limit on your Linux hosted box:
Using "limit" (csh) or "ulimit" (bash) command find out what is the value of "descriptors". As a root user (use sudo) edit /etc/security/limits.conf file.
Close your x term and re-open (or re-connect your NX client) for this change to take effect. System re-start should not be required. If you are not able to increase the limit for some reason using these steps, try a few other things like re-starting your VNC server (or something similar), re-start your Linux box.