Many thanks for catching this Tom - patch applied in trunk.
Eric - do you want to try buiding the 4.2-trunk and seeing if this
fixes your issue?
http://activemq.apache.org/source.html
On 2/22/07, Tom Vijlbrief <[EMAIL PROTECTED]> wrote:
Op woensdag 21 februari 2007 21:05, schreef eccrowe:
> It
Op woensdag 21 februari 2007 21:05, schreef eccrowe:
> It should also be noted that after a client power off, the remaining active
> clients very quickly stop receiving their messages. Server logs still
> appear to be sending messages but the enqueue count is not increasing in
> the jmx-console a
Have deployed 4.1.0 and it appears that things have at least initially not
improved. I am no longer seeing any increase in memory but I am also now
not seeing any consumer removal when the client has been powered off. This
is apparent when examining the jmx console and the activemq server DEBUG
I wonder could you try to reproduce these issues using 4.1.0 on your
platform/hardware?
On 2/16/07, eccrowe <[EMAIL PROTECTED]> wrote:
Greetings,
We are utilizing a client/server (hub/spoke) topic implementation with
ActiveMQ-4.0-RC2 and have noticed a repeatable memory usage increase
reported
