The problem is in theory that the spool locks the messages in memory, therefore two instances of James accessing the same db would be unable to share the locks, and may try to simultaneously process the same message.
I expect you could use configuration to make one instance the reciever, and you could have several recievers, and another (single instance) the transmitter, but that isn't really clustering, more just "crowding round". There was a discussion about making the lock visible as a db field, but AFAIK this hasn't been done yet. d. > -----Original Message----- > From: Chris D [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 4:46 PM > To: [EMAIL PROTECTED] > Subject: Clustering James? > > > Hello, > > I would like to use James strictly as a mail-forwarding server (SMTP). I > have been able to install James and configure the JDBCAlias mailet to > perform forwarding based on a database table. I also intend on > moving the > user repository into the database as well. > > My question is this. Can I have two servers in a cluster running > instances > of James to forward mail? I am assuming that since I am only using SMTP > there should not be a problem. Also, since only one server will be > accepting a given request, there should not be a problem with duplicated > messages. > > Any thoughts? > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.com > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
