james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JAMES-70) Messages lost after server restart
Date Sun, 06 Jun 2004 21:19:54 GMT
Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-70

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-70
    Summary: Messages lost after server restart
       Type: Bug

     Status: Closed
 Resolution: DUPLICATE

    Project: James
 Components: 
             MailStore & MailRepository
   Versions:
             2.1

   Assignee: 
   Reporter: Dejan Nenov

    Created: Tue, 17 Dec 2002 9:31 PM
    Updated: Sun, 6 Jun 2004 2:19 PM
Environment: Operating System: All
Platform: All

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message