Deploying new BPEL processes produce multiple instances in FSW 6
Issue
- We have multiple SwitchYard BPEL orchestrations which run fine when deployed the first time.
- However, if we deploy a newer version of the orchestration the old instance stays in memory and we get 2x the processing of messages through the system (once for the original orchestration instance, once for the newly deployed instance).
- How can we avoid that situation and force the SwitchYard/BPEL orchestration JBoss subsystem to clear out the old orchestration when a new one is deployed?
- Is there a way to troubleshoot orchestrations that are still running, but shouldn't be?
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
