Hi all. I've been working on the POP3 locking problem on multiple instances of james, I found a possibile solution, and It works fine.
I still use James 2.2. It is based on database locking using a "select for update " statement on a user's maildrop (i.e. on a set of records in the inbox table). That's a brief summary of the modifications: POP3Server :reads the new config parameters, gets a valid datasource instance, passes some variables to POP3Handler POP3Handler: locks the resource in doPASS and unlocks it in doQUIT config.xml: new config parameters for pop3server assembly.xml and POP3Server.xinfo: include datasourceSelector, not sure of what I did here JDBCMailRepository: use the same locking connection when removing the messages from the maildrop I did some very db-related modifications and I am working on a more hi-level solution, but I think it will always use the database. If anyone is interested, just give me a shout. Cheers Marcello
