Hi,
We have currently set this option to true however does this need to be
enabled as the performance of the system decreases dramatically when set to
true. The documentation on it just states that it is a jms requirement?
We have a requirement for no message loss so whichever option provides
. With that option disabled, writes are
synced periodically in batches so in the event of a system crash is is
possible that an enqueue is not durable.
Using transactions is another way to avoid the fsync overhead on every
enqueue as it can be deferred till commit.
On 8 April 2010 10:07, Richard Holt
also given that we run in a pure master slave configuration if either fail
could we assume that the disk sync would run on the other activemq instance
(assuming that hasnt failed as well of course!)
--
View this message in context:
Hi,
To generate this error i simply start a pure master slave using kahadb. then
i drop the master part way through processing. wait for test to finish. stop
slave.
remove master data folder. copy slave data folder over (as documented).
start master and slave.
you then get this when browsing
wrote:
yea, I mean on the client producer size. batch up the sends with a
transacted session.
On 8 April 2010 11:20, Richard Holt richard_h...@btopenworld.com wrote:
hi gary, thanks for that it was what i was expecting but the order of
speed
slowdown is vast. for a simple comparison our
Hi,
Our system is distributed where individual services may be offline for an
unknown period of time, during these periods the activemq server is required
to buffer and store the messages. It is not acceptable for us to slow down
producers as we purposefully keep these clients thin and they
Sorry about the thread hijack - however if i have something like this
destinationPolicy
policyMap
policyEntries
policyEntry queue= memoryLimit=1mb
producerFlowControl=false
pendingQueuePolicy
that defaults to 70% of system usage. your config can go to 80%
On 7 April 2010 12:15, Richard Holt richard_h...@btopenworld.com wrote:
Hi Gary,
It appears i am really not understanding this so could you clarify?
You wrote:
Which ever destination tips it over the limit will have its memory
