[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-user
Subject:    Re: Loda balancing james 3
From:       Daniele Marino <danielemarinodm () gmail ! com>
Date:       2012-10-23 20:47:20
Message-ID: 95C32D03-EB4A-4277-AA92-7A35C538838B () gmail ! com
[Download RAW message or body]

Hi,
Thanks for the reply. I can use different istances but i think that don't ensure fault tollerance.
What kind of configuration should i use for the goal?
In general, I would like to know if there are any ideas to realize apache james as a cloud services.
Thanks.


Il giorno 23/ott/2012, alle ore 22:03, Saibabu Vallurupalli <saibabu.vallurupalli@gmail.com> ha scritto:

> Hi Daniele,
> 
> I copied this email to developer forums as well. My understanding of Apache
> James is, there is no built in capability to do load balancing/clustering.
> You need to reply on a load balance out side of Apache James and manager
> traffic routing to different instances of Apache James pointing to same
> database and configurations.
> 
> Eric,
> Please correct me if I am wrong.
> 
> Thank you,
> Sai
> 
> 
> 
> On Tue, Oct 23, 2012 at 3:38 PM, daniele185 <Danielemarinodm@gmail.com>wrote:
> 
>> 
>> Hi,
>> I would like to know how to configure James 3 to have more instances of
>> apache james server, for the load balancing or Fail-Safe of the pop3 and
>> smtp services.
>> Thanks.
>> Daniele
>> --
>> View this message in context:
>> http://old.nabble.com/Loda-balancing-james-3-tp34593381p34593381.html
>> Sent from the James - Users mailing list archive at Nabble.com.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]