Could you please let me know the jira number for this issue fix? I would like to include the link in our documentation so that our customers have full knowledge of this particular fix and could make a knowledgeable decision on the upgrade..
Thanks in advance.. rajdavies wrote: > > The memory model is different for ActiveMQ 4.1 in that for Queues, > only small references to the Queue messages are held in memory. This > means that the Queue depth can be considerably bigger than for > ActiveMQ 3.2.x. > However, our next major release (5.0 nee 4.2) has a more robust model > in that Queue messages are paged in from storage only when space is > available - hence Queue depth is now limited by how much disk space > you have. > > cheers, > > Rob Davies > http://rajdavies.blogspot.com/ > > > On 2 Mar 2007, at 04:47, manav wrote: > >> >> As many of you know, some of the previous versions of ActiveMQ, >> specifically >> that I know of, ActiveMQ 3.2.1 had 'Queue is Full' error problem >> where after >> some persistant messages are stored, the broker results in an error >> 'queue >> is full' and consequently becomes unresponsive. >> >> How is this fixed in ActiveMQ4.1? Is this error guaranteed to not >> happen?or >> could it happen after publishing a greater number of messages? or >> could it >> happen at another time? >> >> We are asking this as we are considering upgrade due to the 'Queue >> is full' >> problem with AMQ3.2.1, but would like to know how it is fixed in >> the later >> releases esp 4.1. >> >> Thanks for any information or pointers.. >> >> >> -- >> View this message in context: http://www.nabble.com/ActiveMQ-4.1- >> Queue-is-full-tf3331665s2354.html#a9263991 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > > > > > > > > -- View this message in context: http://www.nabble.com/ActiveMQ-4.1-Queue-is-full-tf3331665s2354.html#a9270722 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
