[ 
http://issues.apache.org/jira/browse/JAMES-559?page=comments#action_12420040 ] 

Stefano Bagnara commented on JAMES-559:
---------------------------------------

Status update: I wrote a unittest for this and the unittest fail. A good first 
step.

The problem only happens in file repositories because with db repositories we 
don't stream from and to db, while with files we use streaming more 
aggressively.

The problem probably arise from optimizations I added in january about loading 
only headers if only headers are changed and  then write headers from memory 
and stream body from source if no body changes were done. When updating the 
same file there was a check that avoided to update the file when the whole 
message was not changed, but there is no "solution" for only headers changed.

I'm currently investigating these 2 solutions:
1) remove the "load only the headers" optimization and always load/parse the 
full message in memory
2) change the file repository to write to a temporary file and rename it when 
the stream is closed.

I already have found problems with both solutions, and that's why I don't have 
committed a patch yet....


> Message body get lost after call saveChanges() and move to other processor
> --------------------------------------------------------------------------
>
>          Key: JAMES-559
>          URL: http://issues.apache.org/jira/browse/JAMES-559
>      Project: James
>         Type: Bug

>     Versions: 2.3.0b2, 3.0
>     Reporter: Norman Maurer
>     Assignee: Stefano Bagnara
>     Priority: Blocker
>      Fix For: 3.0, 2.3.0b2

>
> After call saveChanges() in a mailet and move the mail to a other processor 
> with ToProcessor the whole messageBody getting lost.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to