glad that helped.
There is a policyEntry expireMessagesPeriod for a destination, it defaults
to 30000 milliseconds so you can reduce that which will ease the processing
of large queue depths or set it to 0 if you don't use a message time to
live.
On 9 April 2010 14:33, moacsjr <moacsjr@yahoo.com.br> wrote:
>
> Thanks Gary!
>
> I have tried 5.3.1 and my application doesn't die. But the "Memory usage"
> message is still there.
> I have discovery that in production I have a lot of messages in queues that
> doesn't have any consumers. So the ActiveMQ Scheduler was working hard on
> every message on this queues at very short intervals. This was causing the
> memory usage to increase very fast. When I deleted the messages every thing
> came back to normal levels.
>
> So I'm working to migrate to 5.3.1 but until there I need to reconfigure
> ActiveMQ Scheduler to a better interval. Any clue?
>
>
>
> Gary Tully wrote:
> >
> > there were a few OOM issues with message expiry and file cursor
> references
> > in 5.3.0 that were resolved in 5.3.1, check the release
> > notes<
> https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520&styleName=Html&version=12183
> >for
> > details. Then try 5.3.1
> >
>
> --
> View this message in context:
> http://old.nabble.com/%28ActiveMQ-Scheduler%29---Memory-usage-change-from%3A-413--of-available-memory%2C-to%3A-414--of-available-memory-tp28172001p28190845.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com