Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of fraser.adams@blueyonder.co.uk
 designates 81.103.221.49 as permitted sender)
Message-ID: <4E455B49.509@blueyonder.co.uk>
Date: Fri, 12 Aug 2011 17:56:41 +0100
From: Fraser Adams <fraser.adams@blueyonder.co.uk>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: Java qpid.max_size in the x-declare in an address appears to
 be unnecessarily limited.
References: <1313131832075-6679380.post@n2.nabble.com>
 <CA+M2XzsFZX=UgukZ7vgkZvP3Axrx5HyZp19ij3sUyPWdQ4wz7g@mail.gmail.com>
In-Reply-To: 
 <CA+M2XzsFZX=UgukZ7vgkZvP3Axrx5HyZp19ij3sUyPWdQ4wz7g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I did wonder, when I tried to trace what was happening I seemed to come 
up to a dead end as nothing seemed to call setMaxSize(). I was beginning 
to think I was going a bit loopy :-)

However my original question remains - is there a limit of 2GB imposed 
anywhere on the queue size created from an Address string as a result of 
an Integer being used instead of a Long. A colleague of mine seems to 
think so.

Cheers,
Frase

Rajith Attapattu wrote:
> Fraser,
>
> That class is not used anymore :)
> We now allow an arbitrary number of arguments within the arguments:{}
> map and no checking is performed.
> I am doing a bit of cleanup and that classes will be removed as part of that.
>
> Regards,
>
> Rajith
>
> On Fri, Aug 12, 2011 at 2:50 AM, fadams <fraser.adams@blueyonder.co.uk> wrote:
>   
>> Hi all,
>> In an address node it's possible to declare a queue and one can set
>> arguments equivalent to administratively declaring a queue by using the
>> x-declare block.
>>
>> I've not had a chance to test this out myself but one of my colleagues
>> suggested that this was limited to 2GB. I've just done a quick grep through
>> /client/src/main/java/org/apache/qpid/client/messaging/address/QpidQueueOptions.java
>> and found the following: (Qpid 0.10)
>>
>>    public void setMaxSize(Integer i)
>>    {
>>        this.put(QPID_MAX_SIZE, i);
>>    }
>>
>> I've not traced any further, but the use of an Integer here rather than a
>> Long would indeed suggest a 2GB limit.
>>
>> Is there a deliberate reason for this or is it a bug/oversight?
>>
>> We're running a C++ broker on a box with 256GB so we're not especially
>> memory limited.
>>
>> I know we can create queues administratively, but we (mostly :-)) trust the
>> broker clients and are working to a trust and verify model and allowing
>> clients to subscribe using their own address specs.
>>
>> Regards,
>> Frase
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/Java-qpid-max-size-in-the-x-declare-in-an-address-appears-to-be-unnecessarily-limited-tp6679380p6679380.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org
>>
>>
>>     
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>   


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org