Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of minfrin@sharp.fm designates
 174.143.229.200 as permitted sender)
From: Graham Leggett <minfrin@sharp.fm>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Tuning activemq for reliability, not performance
Message-Id: <A68B66E8-00F1-45AA-B8E3-B987CDE4747C@sharp.fm>
Date: Tue, 8 Oct 2013 14:18:45 +0200
To: "users@activemq.apache.org" <users@activemq.apache.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))

Hi all,

We have a system that does heavy message processing where we have very =
few (tens, hundreds) of messages that take minutes to process each.

What we also have is periodic activemq v5.8.0 instability that causes =
the "java service wrapper" to proactively send a "kill -9" signal to the =
activemq process. This reverts the queue state right back to where the =
queue was started, and long since processed messages suddenly come back, =
triggering a very expensive message re-processing exercise.

What we want to do is ensure that all memory caching in activemq is =
switched off completely, and all changes are written through to disk at =
all times. We don't care about the performance implications, reliability =
is our number one requirement. If activemq leaks, crashes, we want the =
most recent state practical preserved.

Is this possible?

Regards,
Graham
--