DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15460>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15460 Messages lost after server restart Summary: Messages lost after server restart Product: James Version: 2.1 Platform: All OS/Version: All Status: NEW Severity: Critical Priority: Other Component: MailStore & MailRepository AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Here is the step by step to reporduce the bug. 1. Build & Deploy the Latest James milestone (Phoenix 4.0.1 James 2.1) 2. Start the server and telnet to the admin. 3. Create accounts "u1" and "u2" 4. Setup POP3 clients fro u1 and u2 accounts to "keep mail on server after retrieval". 4. Send email ONLY from u1 to u2. 5. Restart the server. 6. Send email ONLY from u2 to u1. 7. BUG is present: the inbox of u2, which after step (4) had messages from u1 no longer has any messages in it. Problem (as identified by Michael Londarenko at Fasturn): Avalon names the files, used to store the mail messages in the file system in the format hex.RepositoryN.FileStreamSource and headers in format hex.RepositoryN+1.FileObjectStore. N and N+1 are incorrectly re-asigned and used to the inbox for u1 (in step 6 above). It appears that whenever the server is restarted these "N" numbers are reassigned from scratch to each inbox, IN THE ORDER OF INCOMING MESSAGES. It has been suggested that a work-around is to use a SQL DB for storage, however this makes James very hard to deploy for the majority of potential users. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
