aliu wrote:
>
> Hi, just to clarify. In my last post, when I mentioned 'all the pending
> messages are in memory', I actually mean uncommitted messages within a
> transaction. Again, can someone confirm if this statement (all uncommitted
> messages are kept in memory) is true?
>
I am also new
Hi, just to clarify. In my last post, when I mentioned 'all the pending
messages are in memory', I actually mean uncommitted messages within a
transaction. Again, can someone confirm if this statement (all uncommitted
messages are kept in memory) is true?
aliu wrote:
>
> The reason I've been t
The reason I've been trying to figure out these memory limit configurations
is because we have the following use case:
I want to be able to send a large amount of data (>2g) to the queue without
any consumer consuming it for some time, but it seems like active mq
actually keeps all the pending me
Are you validating the XML just to make sure it's not a syntax error?
I get stuff onto disk with a configuration like this (and a producer
sending 1 MB messages):
...
...
Thanks,
Aaron
On Tue, Jul 15, 2008 at
Hi,
Thanks for the quick reply. If I don't want to keep everything in memory,
and I want to be able to set how much should be stored in memory and if
there are more stuff coming, it'd be spilled out to disk, what configuration
settings can I use?
I actually tried setting the destination limits h
I am by no means an authority on this, but I'm not sure the store
usage or temp usage settings are actually used for anything.
I believe you want your memory usage setting to be high enough to hold
all the traffic you expect to be in memory at once. I think this is
e.g. non-persistent messages th
