qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajith Attapattu <rajit...@gmail.com>
Subject Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.
Date Fri, 12 Aug 2011 18:00:32 GMT
On Fri, Aug 12, 2011 at 12:56 PM, Fraser Adams
<fraser.adams@blueyonder.co.uk> wrote:
> 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.

Your colleague is certainly right. All though we don't verify the
parameters, the address parse does treat it as an integer rather than
a long.
So the maximum you can specify is Integer.MAX which ~ 2GB.

Rajith

> 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
>
>

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


Mime
View raw message