An addtional Quota is always created while creating JMSQueue with Ant Scrip

Question

Hi,
When I create JMSQueue on WLS using Ant script, an additional Quota is always being created for each of JMSQueue.
For example, I created a JMS Queue which is named as "CommandQueue", then an Quota will be created which is named as "CommandQueue.Quota".
Following is the script I was using.
<wlconfig url="${weblogic.url}" username="${weblogic.username}" password="${weblogic.password}">
<query domain="${weblogic.domain}" type="Server" name="${weblogic.server}" property="wls.server"/>
<create type="JMSServer" name="JMSServer">
<set attribute="Targets" value="${wls.server}"/>
<create type="JMSQueue" name="CommandQueue">
<set attribute="JNDIName" value="jms/CommandQueue"/>
<set attribute="MessagesMaximum" value="-1"/>
</create>
</create>
</wlconfig>
Is there anyone who can tell me how to solve this issue?
Thanks very much.

Answer 1

Repro:
1.Launch JDev 11.1.1.5.0
2.Start the instance of Integrated WLS
3.Run "doconfig" task from following script.
build.properties
weblogic.home.dir = D:/Oracle/Middleware/wlserver_10.3
weblogic.lib.dir = ${weblogic.home.dir}/server/lib
weblogic.url = t3://localhost:7101
weblogic.username = weblogic
weblogic.password = weblogic1
weblogic.domain = DefaultDomain
weblogic.server = DefaultServer
build.xml
<?xml version="1.0" encoding="UTF-8" ?>
<project default="doconfig">
<property file="deploy.properties"/>
<path id="jar.path">
<pathelement location="${weblogic.lib.dir}\weblogic.jar"/>
</path>
<echo message="Initial WLS taskdef."/>
<target name="init" description="Initialize WLS taskdef">
<taskdef name="wlserver" classname="weblogic.ant.taskdefs.management.WLServer" classpathref="jar.path"/>
<taskdef name="wlconfig" classname="weblogic.ant.taskdefs.management.WLConfig" classpathref="jar.path"/>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" classpathref="jar.path"/>
</target>
<echo message="Deleting existing configuration"/>
<target name="clean" depends="init" description="Delete existing configuration.">
<wlconfig url="${weblogic.url}" username="${weblogic.username}" password="${weblogic.password}" failonerror="false">
<delete Mbean="${weblogic.domain}:Name=JMSServer,Type=JMSServer"/>
<delete Mbean="${weblogic.domain}:Name=QueueFactory,Type=JMSConnectionFactory"/>
</wlconfig>
</target>
<echo message="Doconfig"/>
<target name="doconfig" depends="clean">
<!--Login-->
<wlconfig url="${weblogic.url}" username="${weblogic.username}" password="${weblogic.password}">
<query domain="${weblogic.domain}" type="Server" name="${weblogic.server}" property="wls.server"/>
<!-- When creating a new JMS server, the script uses a nested create element to create a JMS queue, which is the child of the JMS server -->
<create type="JMSServer" name="JMSServer">
<set attribute="Targets" value="${wls.server}"/>
<create type="JMSQueue" name="RequestQueue">
<set attribute="JNDIName" value="jms/RequestQueue"/>
<set attribute="MessagesMaximum" value="-1"/>
</create>
<create type="JMSQueue" name="ResponseQueue">
<set attribute="JNDIName" value="jms/ResponseQueue"/>
<set attribute="MessagesMaximum" value="-1"/>
</create>
<create type="JMSTopic" name="NotificationTopic">
<set attribute="JNDIName" value="jms/NotificationTopic"/>
<set attribute="MessagesMaximum" value="-1"/>
</create>
</create>
<!-- The script creates a new JMS connection factory using nested set elements -->
<create type="JMSConnectionFactory" name="QueueFactory">
<set attribute="JNDIName" value="jms/QueueFactory"/>
<set attribute="XAServerEnabled" value="true"/>
<set attribute="Targets" value="${wls.server}"/>
</create>
</wlconfig>
</target>
</project>
4. Login to WLS admin console
5. Home >JMS Modules >interop-jms
6. You can see following additional Quota were getting created for each of Queue/Topic which is unncessary.
NotificationTopic.Quota
RequestQueue.Quota
ResponseQueue.Quota