JMS Consumers Are Not Balanced Within All Members Of A Distributed Topic When Using Destination Availability Helper
Last updated on JUNE 02, 2017
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 12c]
Information in this document applies to any platform.
The issue is related with how consumers are balanced in a distributed topic when there is an application using Destination Availability Helper (DAH) in WebLogic Server 126.96.36.199. The problem is that consumers do not get balanced after JMS server restarts when they use an application that connects using the Destination Availability Helper.
Customized frameworks are used to standardize application development (named FWK2 for applications using DAH and FWK3 for applications using MDBs). (Note: FWK is an acronym used for Framework for an application)
To gather information locally testing applications have been used with each framework. Different cases have been tested locally and results are summarised below:
- When JMS servers are active, and any application is activated, they successfully connect and all consumers are balanced within the 4 jms servers.
- Restarting one or more servers in the JMS domain causes that when they become active again, consumers are recreated unevenly in the restarted servers (unbalanced).
- Consumers are unbalanced only when an application FWK2 (using DAH) is active. This means that when an MDB application is active and the FWK2 is not, restarting JMS servers does not produce unbalancing of consumers.
However, if a FWK2 application is active, it causes unbalancing, even to a MDB application that is deployed in a different domain.
- Versions of each application using Foreign JMS Servers and connecting directly to the JMS WLS Domain have been used, with identical results.
Identical scenarios have been tested with WLS 12.1.3 and consumers are balanced correctly. Besides, a test case with the JMS domain in WLS 12.1.3 and Apps domains in WLS 12.1.2 showed that connections were unbalanced (not in the other case).
So, it is the WLS version used in the servers where the FWK2 application is deployed what mainly causes incorrect consumer balancing.
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