Yeah,

I was thinking about separate outgoing spools (local, file based) and one
shared master db for emails storage.

Is that your setup?

Thanks
On Oct 15, 2012 3:18 PM, "Massimo Romanazzi" <[email protected]>
wrote:

> Hi,
> we dit it with success even if it is not properly a "Cluster".
> Used a database repository (Oracle) but we need to have different spool
> one for each server (three at the moment). There is no master server.
> We didn't try with shared FS.
> Hope this helps.
> Regards,
> Pietro
> > Thanks for this.
> >
> > Any particular reason why shared db repo will not work?
> >
> > I think I should be able to achieve what I need with file based repo +
> one
> > active james + one in passthrough (via gateway params) mode.
> >
> > Incoming messagss will be accepted by both nodes but only one will really
> > process them (mailets + store).
> >
> > In case of fail of master james I can switch passthrough one into master
> > mode and use shared storage(running on 3rd host)... Does it sound
> > reasonable?
> >
> > Cheers
> >  On Oct 12, 2012 1:38 PM, "Eric Charles" <[email protected]>
> > wrote:
> >
> >> What you describe is not possible.
> >> James 2.3 has no clustering option, nor James 3 a this time.
> >>
> >> Thx, Eric
> >>
> >>
> >> On 12/10/2012 09:57, Hamster wrote:
> >>
> >>> Hi lads,
> >>>
> >>> Will I hit any issues if I setup two James instances to access same
> >>> file
> >>> based repository?
> >>>
> >>> Is it possible that outgoing emails will be set twice(under heavy
> >>> load)?
> >>>
> >>> If it is not possible - if I switch to db based repositories - will it
> >>> solve my problems?
> >>>
> >>> Thanks for any help.
> >>> Cheers
> >>>
> >>>
> >> --
> >> @echarles
> >>
> >>
> ------------------------------**------------------------------**---------
> >> To unsubscribe, e-mail:
> >> server-user-unsubscribe@james.**apache.org<
> [email protected]>
> >> For additional commands, e-mail:
> >> [email protected].**org<[email protected]>
> >>
> >>
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to