Redeploying a BPEL process with same revision number is throwing error in SOA 10.1.3.5

I was trying to deploy a simple HelloWorld process and got following error :

<2011-02-09 16:10:26,934> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "domain manager": Error deploying BPEL suitcase.
An error occurred while attempting to deploy the BPEL suitcase file "/u201/soal/oracle/product/10.1.3/soa/bpel/domains/default/tmp/bpel_8916679.tmp"; the exception reported is: P
rocess bpel://localhost/default/HelloWorld~1.0/ is being re-deployed to a Production Server with same revision number.Please modify the revision for the process.

ORABPEL-05250

Error deploying BPEL suitcase.
An error occurred while attempting to deploy the BPEL suitcase file "/u201/soal/oracle/product/10.1.3/soa/bpel/domains/default/tmp/bpel_8916679.tmp"; the exception reported is: P
rocess bpel://localhost/default/HelloWorld~1.0/ is being re-deployed to a Production Server with same revision number.Please modify the revision for the process.

at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:783)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:464)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

To resolve this issue

Log in to BPELAdmin console


http://localhost:port/BPELAdmin


Check for the value of server mode.


Change it to development and try to deploy your process.


In production mode redeployment with same revision number is not allowed.


The same has been mentioned in the Oracle document

It says

With this release, a new property named serverMode has been added to Oracle BPEL Admin Console. You can set this property to the following values:

production � Redeployment of the process with the same revision is not allowed.

development � Redeployment of the process with the same revision marks the existing instance as stale.

promiscuous - Redeployment of the process with the same revision does not make the instance stale. Work items are migrated.

If you are on a clustered environment, then look for property <property id="productionServer"> in your collaxa.config.xml

It will look something like this

<property id="productionServer">
<name/>
<value>true</value>
<comment/>

Change this value to false as this value will take precedence over the one that you have mentioned in BPELAdmin console.

Once you make the changes try to redeploy and this should work now.