Redeploying JMS Adapter After Plan Change Causes All Consumer Connections To Break
Last updated on SEPTEMBER 12, 2017
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Technology Adapters
Redeploying JMS Adapter after plan change causes all consumer connections to break
Every time JMS Adapter is updated or redeploy due to new config plan changes, it will break all existing JMS Consumer connections and will not restore automatically.
How can we recover from this without complete SOA Cluster restart?
weblogic.jms.common.IllegalStateException: [JMSClientExceptions:055088]The consumer is closed.
The issue can be reproduced at will with the following steps:
1) Have a SOA Composite Deployed consuming from JMS Queue
2) Make JMS Adapter Outbound Connection Pool Configuration Change
3) Update JMS Adapter and select "Redeploy this application using the following deployment files:" with update Config Plan
4) Activate changes
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms