Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-08-03 Thread wuxz
As rajdavies said, you can wait for v5.2, or you can check the queue size before sending message frequently? replyramdas wrote: > > Anything will do as long as we know the boundry condition. Let me know how > can we do this. Thanks in advance, waiting for the reply > > > regards > Ramdas >

Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-08-03 Thread Ramdas Sawant
Anything will do as long as we know the boundry condition. Let me know how can we do this. Thanks in advance, waiting for the reply regards Ramdas On 8/4/08, wuxz <[EMAIL PROTECTED]> wrote: > > > Do you want to get an Exception been thrown when you call the > Producer.send() > method, or you ju

Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-08-03 Thread wuxz
Do you want to get an Exception been thrown when you call the Producer.send() method, or you just want to get an asynchronous advisory message? Bala M wrote: > > Hi, > > Could you please explain usage of the elements "memoryUsage, storeUsage > and tempUsage"? I searched this forum, but I am no

Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-07-27 Thread Rob Davies
In version 5.2 - we can optionally send advisories when limits are reached - see http://activemq.apache.org/advisory-message.html Hopefully 5.2 will be released soon cheers, Rob On 28 Jul 2008, at 06:25, Ramdas Sawant wrote: Hi all, Any thoughts on the below question I am reall

Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-07-27 Thread Ramdas Sawant
Hi all, Any thoughts on the below question I am really stuck with this activity Thanks in advance Regards Ramdas On 7/25/08, Ramdas Sawant <[EMAIL PROTECTED]> wrote: > > Hi all, > Even i am looking forward for the explaination. My initial > assumption turned out to be

Re: Memory Usage limit in ActiveMQ 4.1.2 and ActiveMQ 5.1.0

2008-07-25 Thread Ramdas Sawant
Hi all, Even i am looking forward for the explaination. My initial assumption turned out to be false. I thought setting will limit my publishing of messages once the data file size reaches 1mb (in case of persistent messages and durable subscriber not being active). But what is really hap