Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 534008

Summary: Need mechanism to specify the queue size of a queue that is setup via the Java API.
Product: Red Hat Enterprise MRG Reporter: apestel
Component: qpid-javaAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED ERRATA QA Contact: Jiri Kolar <jkolar>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1CC: gsim, jkolar, nobody
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
This update introduces a mechanism that specifies the queue size of a queue that is setup via the Java API.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 16:15:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description apestel 2009-11-10 02:15:14 UTC 
Need mechanism to specify the queue size of a queue that is setup via the Java API.  

From mailing list:  "The issue here is with 'queues' (in the AMQP sense, not in the JMS sense) created 'under the covers' for topic subscriptions. These cannot be statically setup in advance. At present the only option is to control the default queue size as there is apparently no way to configure the JMS client to create subscription queues with specified configuration."

Example might be something like this utilizing the existing JNDI property type approach:

destination.queue=direct://amq.direct//message_queue?routingkey='routing_key'&queueSize=1000000
Comment 1 Rajith Attapattu 2010-02-18 03:51:39 UTC 
Support for the above is added via the new addressing syntax.
Ex.

"ADDR:my-queue/hello; { " + 
                        "create: always, " +
                        "node-properties: {" + 
                             "durable: true ," +
                             "x-properties: { " + 
                                 "auto-delete: true," +
                                 "'qpid.max_size': 1000," +
                                 "'qpid.max_count': 100," +
                             "}" +
                        "}" +
                      "}";

This string could be passed into the following method
Queue queue = session.createQueue(addrStr);

Or use it in the jndi.properties file.

It's available from rev 906145 and upwards in Qpid trunk.
Comment 3 Jiri Kolar 2010-09-20 14:18:29 UTC 
Yes new ADDR mechanism is present in qpid-java-client-0.7.946106-9 and allow this

validated on RHEL5.5/RHEL4  i386 / x86_64  

packages:
# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u

openais-0.80.6-16.el5_5.7
openais-devel-0.80.6-16.el5_5.7
python-qpid-0.7.946106-14.el5
qpid-cpp-client-0.7.946106-15.el5
qpid-cpp-client-devel-0.7.946106-15.el5
qpid-cpp-client-devel-docs-0.7.946106-15.el5
qpid-cpp-client-ssl-0.7.946106-15.el5
qpid-cpp-mrg-debuginfo-0.7.946106-14.el5
qpid-cpp-server-0.7.946106-15.el5
qpid-cpp-server-cluster-0.7.946106-15.el5
qpid-cpp-server-devel-0.7.946106-15.el5
qpid-cpp-server-ssl-0.7.946106-15.el5
qpid-cpp-server-store-0.7.946106-15.el5
qpid-cpp-server-xml-0.7.946106-15.el5
qpid-java-client-0.7.946106-9.el5
qpid-java-common-0.7.946106-9.el5
qpid-tools-0.7.946106-10.el5
rhm-docs-0.7.946106-5.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53

->VERIFIED
Comment 4 Martin Prpič 2010-10-10 11:35:47 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
This update introduces a mechanism that specifies the queue size of a queue that is setup via the Java API.
Comment 6 errata-xmlrpc 2010-10-14 16:15:03 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html