MAX-BEANS-IN-FREE-POOL not Being Picked when Using Wldeploy and Appversion (Doc ID 1942182.1)

Last updated on OCTOBER 11, 2023

Applies to:

Symptoms

The JMS Consumers Count of the Queue is not displaying the configured value in max-beans-in-free-pool when using wldeploy. The same application deployed using WebLogic console displays the configured value.

Steps to reproduce the issue:

1. Configure a Cluster with 2 managed servers. Cluster-0 => Server-0, Server-1
2. Configure a JMSServer target to the one of the managed servers. JMSServer-1
3. Configure a JMS Module and 2 Resources:
   
   1. JMS Module => SystemModule-1
   2. Connection Factory => ConnectionFactory-1, JNDI Name => ConnectionFactory-1, Sub deployment => sdcluster, target => JMSServer-1
   3. Queue => Queue-1, JNDI => Queue-1, Sub deployment => sdcluster, target => JMSServer-1
4. Configure a Work Manager. WorkManager-0, target => Cluster-0, Maximum Threads Constrains => 20
5. The application has been configure to use <max-beans-in-free-pool>18</max-beans-in-free-pool> AND <dispatch-policy>WorkManager-0</dispatch-policy>
6. Deploy the attached application TestMDBWM.ear using the console.
7. Go to JMS Modules >SystemModule-1 >Queue-1 > Monitoring. It shows Current Consumers = 18 as expected.
8. Delete the application.
9. Place TestMDBWM.ear and attached build.xml in a directory /mydir. Snippet of build.xml:
   
   The application is deployed successfully.
10. Go to JMS Modules >SystemModule-1 >Queue-1 > Monitoring. Current Consumers = 16. Hence, it is not picking max-beans-in-free-pool configured when using appversion If appversion="1.0" is removed from the ant script, Current Consumers = 18 as expected.

The issue does not occur in WebLogic Server 10.3.6.0.9.

Changes

Cause

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