activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: First configuration steps
Date Thu, 25 Oct 2018 13:04:32 GMT
If you haven't yet installed ActiveMQ, good information is at

For security, that depends a little on how much you want to secure the
broker and what technologies you're using (for example, do you want to
secure the web console? authenticate producers and consumers? integrate
with LDAP?), but some useful links are,,, and The true
MVP is, of course, to do none of those, but the appropriateness of how much
security is needed and what kind depends heavily on how you plan to use and
expose the broker and on your organization's approach to security and risk,
so there's no one-size-fits-all answer here.

For things to make sure you think about, I'd focus on protecting the broker
from being sent too much data ( and on how to handle
slow consumers (


On Thu, Oct 25, 2018, 1:29 AM nvsteenselvanderaa <> wrote:

> /What are the first configuration steps to take to get a minimum viable
> ActiveMQ instalation?/
> This seems a question you would never want to ask, nor does it seem a
> question i would want to answer when it's regarding a piece of software i'm
> responsible for and have spent months/years training on.
> However, needs must, and i'l try to explain it a bit.
> Our company is currently running some PoC's on several pieces of software,
> our team (Mule ESB) has to connect all those services to our existing
> backend.
> Two separate services need a message queue installed somewhere on your
> servers to function properly, however our company does not have anyone
> inhouse with experience in ActiveMQ. Our team has been given the task of
> installing and configuring these queue's, we told mgmt we would do it but
> that since there's no experience on the software it would not be production
> proof.
> So to recap:
> Knowing that this installation will not be used for production data, what
> steps do we take to make it:
> At least basicaly secured.
> Configure the recources it's using from the server (single/multi thread?)
> And more importantly, what are the things we're likely to run into or
> overlook?
> Now i know that this is a lot, and that my first reaction would be to tell
> me to google it.
> But it's now cost two persons a day, and so far we have not found a single
> clear page on what to do.
> --
> Sent from:

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