Wow, I didn't see that this thread had continued. It would truly be great if some of these existing scenarios / strategies were added to the Wiki and/or the FAQ.
On 3/9/07, sunsetartproducts <[EMAIL PROTECTED]> wrote:
I use this set-up for the whitelist and spam analysis with 2 instances of James 2.3.0 on different servers sharing a MySql database on a third server. One machine is the fallover machine the other the primary mail server. I have not tried using the database to hold the mails, just the whitelist and spam database. But at least in theory Mysql would allow access by two different instances, as the file locking in MySQL is at the database level. When I am using it in this way, I can add or remove data from the database from either mail server, MySQL just waits to finish the first process before committing to the next. (not much of a wait as the processes take only a millisecond or less.) Of course the servers are only 10 feet apart and have only one hop on a switch to navigate. If you are using a file system repository for the mails data instead of a SQL Server database, then you would run into the problem of file locking if the two servers were trying to access the same files on the hard drive at the same time. John G. Norman-2 wrote: > > Stephano, > > THANKS. > > John > > On 3/8/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >> >> You can't use the same db table for 2 different repositories instances >> because the locking is at an application level. You would need to >> rewrite a distributed locking support (someone did something about this >> in past: see james-ha project on sourceforge). >> > > -- View this message in context: http://www.nabble.com/Multiple-James-instances-can-use-database-repository--tf3369616.html#a9406721 Sent from the James - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
