Hi. I submitted the bug, I worked on it and I think I solved it, using a modified Lock class to lock the user in POP3Handler.doPASS and unlocking the user in POP3Server.doQUIT. In POP3Handler.doPASS there is a lock-check in an infinite loop with a 10 secs wait if it the user is locked and a break when the resource is freed.
I think it works fine in a single james instance environment. I am thinking at a solution for a failover configuration environment, maybe a locking system via web service. Ciao Marcello > Stefano Bagnara wrote > [...] > > I'm pretty sure that we don't lock the repository. > Can you submit this issue to our issue tracker? > https://issues.apache.org/jira/browse/JAMES > > Thank you, > Stefano > > > PS: I reposted this message 'cause of mail problems; if it's > > duplicated I apologize > > PS: I confirm we received it twice. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
