My Oracle Support Banner

How to Keep the Running Instances on after Redeploying a Composite with the Same Revision ID (Doc ID 1608512.1)

Last updated on AUGUST 06, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

While trying to redeploy a composite application with same revision Id by selecting the check box "Keep the running instances on after redeployment" in JDeveloper, the following error is seen.

ERROR
-----------------------

[03:15:16 PM] Error deploying archive sca_ProjectTest1_rev1.0.jar to partition "default" on server 
[03:15:16 PM] HTTP error code returned [500]
[03:15:16 PM] Error message from server:
There was an error deploying the composite on server: Operation failed - Member(Id=1, Timestamp=2013-11-15 11:28:21.646, Address=72.37.11.219:26795, MachineId=xx, Location=site:,machine:xx,process:27502, Role=WeblogicServer):Error occurred during deployment of component: BPELProcess to service engine: implementation.bpel, for composite: Project: ORABPEL-05253

Cannot re-deploy a durable process.
Cannot re-deploy a durable process "BPELProcess" with keepInstancesOnRedeploy=true.
A durable BPEL process cannot be deployed when the flag keepInstancesOnRedeploy is set to "true".
Remove the keepInstancesOnRedeploy flag and try again.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In JDeveloper, redeploy a composite application with the same revision ID by selecting the check box "Keep the running instances on after redeployment".



Cause

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
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.