Re: [xep-support] Queueing in EnMasse

From: Khachik Kocharyan <>
Date: Mon Sep 01 2008 - 02:05:34 PDT

Hi Robert,

you can use
<option name="agents-count" value="INTEGER"/>

The default value is XEP server's count in EnMasse configuration file.
With a greater 'agents-count' EnMasse starts more agents and can
handle more connections.
There is one option to control logging:
<option name="log-level" value="'all'|'error'|'none'"/>


On Օգս 28, 2008, at 17:01, Robert Goldsmith wrote:

> Hi all,
> We are using EnMasse with it's SOAP interface, Fairy, to manage a
> cluster of XEP instances but we are having problems with queueing
> submitted jobs. We have our own front-end (we call it Eiocha) and
> this does lots of pre-processing and central handling of binary
> files etc. before then sending the xsl-fo onto EnMasse for
> processing. However, if we try to send more SOAP requests than
> there are instances of XEP, EnMasse effectively hangs. When we then
> kill the SOAP connections, EnMasse then throws an exception and
> crashes out. EnMasse does not seem to have very much control over
> logging and letting us know what it is having problems with so we
> can't really tell what's going on. If we throttle the connections
> it works fine (although nothing ever shows up listed in the
> 'submitted' section of the web status page) but if it's not going
> to do queueing we might as well not bother with EnMasse and talk
> directly to the XEP instances.
> Has anyone seen a similar problem? Or know how to turn on
> additional logging?
> If we did decide to dump EnMasse and talk to XEP directly, do we
> need to pay for an additional product or is there some sort of tcp-
> based comms available as part of the standard XEP package (or as
> part of the EnMasse license)? We are developers so we are not going
> to be phased by complex protocols (we are just lazy and would
> prefer it if EnMasse did it for us!) :)
> Thanks in advance,
> Robert
> ---
> Robert Goldsmith
> Systems Integrator
> SP Group
> "Please consider the environment before printing this e-mail"
> **********************************************************************
> *************
> IMPORTANT - this email and the information that it contains may
> beconfidential, legally privileged and/or protected by law. It is
> intendedsolely for the use of the individual or entity to whom it
> is addressed. If you are not the intended recipient, please notify
> the sender immediatelyand do not disclose the contents to any other
> person, use it for any purpose,or store or copy the information in
> any medium (including by printing it out. Please also delete all
> copies of this email and any attachments from yoursystem and shred
> any printed copies.
> We do not accept any liability for losses or damages that you may
> sufferas a result of your receipt of this email including but not
> limited tocomputer service or system failure, access delays or
> interruption, datanon-delivery or mis-delivery, computer viruses or
> other harmful components.
> Any views expressed in this message are those of the individual
> senderexcept where the sender specifically states them to be the
> views of the SP Group.
> Copyright in this email and any attachments belongs to the SP Group
> the sender orits licensors.
> **********************************************************************
> *************
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-
> support'
> in the body of the message to from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of
> Service

(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
Received on Mon Sep 1 03:09:44 2008

This archive was generated by hypermail 2.1.8 : Mon Sep 01 2008 - 03:09:48 PDT