Hello all,
I'm seeking thoughts from those in the community who have been using
Qpid in mission critical systems.
So from my observations Qpid seems pretty stable, but there's alway the
possibility of exciting little gotchas especially as the complexity
grows and one starts to use fairly complex federated topologies of large
numbers of brokers. As an example in the early days we got bitten a lot
by "blown" links when consumers went down and queues filled to capacity.
We're working past that with queue routes/circular queues/servers with
largish memory etc.
Despite all that I'm expecting some gotchas so I want to turn my
attention to managing/monitoring/system health check.
So what sort of things are others in similar positions using?
The core tools qpid-config, qpid-route, qpid-stat etc. are very useful
but they are quite "mandraulic" so are people manually using those and
reactively solving problems or is there much in the way of proactive
management (fixing things before the clients shout :-) Are people
scripting the core tools or writing their own stuff? I've been doing a
lot with QMF2 lately and there's clearly a huge potential with that, but
I don't want to go about reinventing wheels.
Has anyone else integrated Qpid with Enterprise System Management tools
such as HP OpenView/OperationsManager? If so are they writing bespoke
QMF Console apps or scripting things like qpid-stat, qpid-printevents etc.
I'd be interested to know what the recommended approaches are and
whether there are any "sister projects" looking into this - I'd like to
keep things cohesive with best practice and I'd like to avoid going down
divergent paths.
Hope to hear from you
Cheers
Frase
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
