----- Original Message -----
From: "Prasanna Uppaladadium" <[EMAIL PROTECTED]>
> Hello.
>
> Could the active developers on this list please comment on the
> scalability of James? In particular, I would like to know how to
> configure James so that multiple server processes can be used for
> processing mails in harmony - i.e., using standard process replication.
>
> Comments much appreciated,
> Prasanna.
The changes going into the 1.2.1 release should noticeably help scalability,
particular the removal of "synchronized" on the mail spool methods. Out of
the box, James is configured for 1 spool manager thread which can be changed
by editing the tag with the same name in JAMES.conf.xml. This has not been
fully tested, so you might want to test this.
However, unless you create a very complex mail processing system that
involves lengthy checks (virus scanning), you probably will not need to
increase this number. The largest bottleneck usually is with remote
delivery. By default there is one thread that attempts to deliver messages
remotely, and this can be increased by adding a deliveryThreads property to
the RemoteDelivery mailet. An example configuration would look like this:
<mailet match="All" class="RemoteDelivery">
<outgoing> file://../var/mail/outgoing/ </outgoing>
<!-- <outgoing> town://mail-outgoing </outgoing>-->
<delayTime> 21600000 </delayTime>
<maxRetries> 5 </maxRetries>
<deliveryThreads> 3 </deliveryThreads>
</mailet>
This is very useful as the speed of the remote SMTP servers can vary greatly
from a few seconds to several minutes for delivery.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
