You should be able to run two instances of James with one Database, the database would just wait for one process to finish before starting the next. The databases are built to handle heavy loads.
The problem I see is that you can't run two instances of James on the same machine both trying to have exclusive use of the same port (25 and 110) the first insstance would run and the second instance would crash since it couldn't get exclusive use of the port. IF you had two instances of James runnig on two different servers, but accessing the same database, that would theoretically work. Hi all. Does anybody use two or more instances of James with one database backend? -- View this message in context: http://www.nabble.com/two-or-more-instances-of-James-with-one-database-backend-tf3291532.html#a9406445 Sent from the James - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
