Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread fadams
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

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Rajith Attapattu
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

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Fraser Adams
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

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Gordon Sim
On 08/12/2011 05:56 PM, Fraser Adams 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

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Fraser Adams
So was this actually a broker related thing rather than a Java client runtime thing - looks like it from the JIRA? I could have *sworn* that I'd created queues of 5 or 6 GB administratively via qpid-config a while back, did I imagine that or is it a different part of the code that handles

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Gordon Sim
On 08/12/2011 06:25 PM, Fraser Adams wrote: So was this actually a broker related thing rather than a Java client runtime thing - looks like it from the JIRA? Yes I could have *sworn* that I'd created queues of 5 or 6 GB administratively via qpid-config a while back, did I imagine that or is

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Gordon Sim
On 08/12/2011 05:39 PM, Rajith Attapattu wrote: We now allow an arbitrary number of arguments within the arguments:{} map and no checking is performed. How are integers treated? They aren't all converted to ints are they? -

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Rajith Attapattu
On Fri, Aug 12, 2011 at 1:36 PM, Gordon Sim g...@redhat.com wrote: On 08/12/2011 05:39 PM, Rajith Attapattu wrote: We now allow an arbitrary number of arguments within the arguments:{} map and no checking is performed. How are integers treated? They aren't all converted to ints are they?

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Rajith Attapattu
On Fri, Aug 12, 2011 at 12:56 PM, Fraser Adams fraser.ad...@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

Re: Java qpid.max_size in the x-declare in an address appears to be unnecessarily limited.

2011-08-12 Thread Fraser Adams
Rajith, could you please look into fixing that in a future release? BTW I totally agree with your comment Btw I think it's quite ugly to have a user specify queue sizes in large numbers. We should allow it to be specified in bytes, MB's and GB. Ex qpid.max_size=13334553 (treat it as bytes)