Hi Peter,
This means there is a known issue with very high volume Queues/
durable subscribers in 4.x that is being addressed in the next release.
I wouldn't recommend you go with the next release in production
however, not all the functionality is tied down yet.
You could either help contri
Does this mean "this is a known bug in 4.1 and has been fixed", or "take
4.2-snapshot for a spin, and maybe it helps?"
We're running 4.1 in production, and this and other memory leaks (e.g.
the whole issue revolving around disconnect() not working with durable
topics) are causing major probl
Hi Rob,
does that mean the persistence is broken in 4.1 ? will you be updating the
4.2 release time line ? For now, I want to measure the performance impact of
using persistence and also see if it would solve the out of memory problem.
- Sandeep
--
View this message in context:
http://www.nab
Hi Sandeep,
I think using the latest snapshot for 4.2 will help:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
activemq/apache-activemq/4.2-incubator-SNAPSHOT/
cheers,
Rob
On 5 Feb 2007, at 15:20, Sandeep Chayapathi wrote:
Hi all,
As a followup to these questions:
h
