MAX-BEANS-IN-FREE-POOL not being Picked when using wldeploy and appversion
Last updated on NOVEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.
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:
- Configure a Cluster with 2 managed servers. Cluster-0 => Server-0, Server-1
- Configure a JMSServer target to the one of the managed servers. JMSServer-1
- Configure a JMS Module and 2 Resources:
- JMS Module => SystemModule-1
- Connection Factory => ConnectionFactory-1, JNDI Name => ConnectionFactory-1, Sub deployment => sdcluster, target => JMSServer-1
- Queue => Queue-1, JNDI => Queue-1, Sub deployment => sdcluster, target => JMSServer-1
- Configure a Work Manager. WorkManager-0, target => Cluster-0, Maximum Threads Constrains => 20
- The application has been configure to use
- Deploy the attached application TestMDBWM.ear using the console.
- Go to JMS Modules >SystemModule-1 >Queue-1 > Monitoring. It shows Current Consumers = 18 as expected.
- Delete the application.
- Place TestMDBWM.ear and attached build.xml in a directory /mydir. Snippet of build.xml:
The application is deployed successfully.
- 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.
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