[ http://issues.apache.org/jira/browse/JAMES-371?page=all ]
Stefano Bagnara resolved JAMES-371:
-----------------------------------
Fix Version: 2.3.0a2
Resolution: Won't Fix
The patch submitted was invalid.
I changed many code that could have optimized the spoolmanager but the change
proposed in the issue is not applicable: to further improve the spooling we
should change the spoolmanager interface.
> Speed improvement in SpoolManager
> ---------------------------------
>
> Key: JAMES-371
> URL: http://issues.apache.org/jira/browse/JAMES-371
> Project: James
> Type: Improvement
> Components: SpoolManager & Processors
> Versions: 2.3.0a1
> Environment: James SVN branch truck-merged 20050504.
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Priority: Minor
> Fix For: 2.3.0a2
> Attachments: JamesSpoolManager.java.patch, JamesSpoolManager.java.patch,
> LinearProcessor.java.patch
>
> Processor invoke store() on the spool when a message change its state but the
> message is still lockend and the notify called by the spool does not work (As
> far as I understand).
> I removed spool.store from the processor and leave spool handling to the
> spoolmanager thread.
> I also added a loop to the run of the spoolmanager thread so that it will
> process every state till GHOST or ERROR and not only one state at a time.
--
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]
