Ok, ill add it to the end of the todo list. It needs changes to the queue and mbean methods to work, and the API versioning to put it in the console. Also, upon inspection the resultant TabularData sets also appear to only hold 2^31 messages, so short of implementing a Qpid specific list and requiring JConsole etc users make that class available to use the results, viewMessages(from, to) would still need be limited to viewing at most 2^31 at a time...just any 2^31 instead of the first 2^31 as at present.
2009/6/24 Aidan Skinner <[email protected]> > On Tue, Jun 23, 2009 at 8:07 PM, Robbie Gemmell <[email protected] > >wrote: > > > > That's what I was thinking after I realised how it was actually doing > > things, though you might struggle to understand that from my first email > as > > I noticed that there are a few key words missing while I was deleting it > to > > send this...(which took a while on the phone:p) > > > Given that there isn't, AFAIK, any inherent limitation in the broker on max > queue size I'm a little hesitant to pass up this opportunity to fix it > properly and use Long. > > Other bits of the API are equally short sighted, but at the end of the day > SimpleQueueEntryList is your classic linked list which can scale beyond > 2^31. > > - Aidan > > -- > Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org > "A witty saying proves nothing" - Voltaire >
