SOA 11g: JMS Adapter Suspension is not Performed in Parallel, Causing Suspension to Timeout and Fail
Last updated on NOVEMBER 03, 2016
Applies to:Oracle SOA Platform - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In a standalone application the JMS Adapter binds its own JMS connection factory into a local JNDI tree. The CF sleeps for two seconds, then fails.
The application then simply configures 5 inbound JMS adapters that use this CF. When the application is undeployed, the JMS Adapter suspend can take up to two seconds, and blocks synchronously. This is the bug - the adapter should process any operation that might take some time asynchronously, which would allow the framework to shutdown the adapters in parallel.
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