activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Poloney" <>
Subject Re: Basic queue concept
Date Thu, 03 Apr 2008 07:33:40 GMT
On Thu, Apr 3, 2008 at 12:19 AM, Arjen van der Meijden <> wrote:

> My consumer just consumes a message, processes it and then goes on waiting
> for another one. So if that message happens to be a 'kill'-message, it dies
> (if the message was sent after the consumer started).
> When I shutdown those consumers using their init.d-scripts, the
> init.d-scripts sends both a normal sigint and one of those kill-messages to
> make sure the script gets interrupted anytime soon. For the million-messages
> consumer, that isn't really necessary, but for the few-hundred consumer it
> is quite usefull to wake it up, so it can die right away.

:) Awesome. I totally understand now.

> One of the reasons to start using these consumers was indeed to facilitate
> batch processing, although I haven't implemented such a feature yet. But I
> wouldn't worry too much about memory leaks, as long as you clean up the data
> afterwards and maybe keep away from using too fancy resources and too
> complex object trees.
> I would however add some more clean-kill stuff, so the current internal
> list is processed cleanly, prior to dieing.

I don't anticipate doing any XML or DOM parsing here, but I'll keep that in
mind for the future. Thanks again for all your help!


-- Joel

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message