james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wiederkehr (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (MIME4J-89) Improve thread synchronization in MultiReferenceStorage
Date Mon, 01 Dec 2008 18:03:44 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Markus Wiederkehr updated MIME4J-89:
------------------------------------

    Attachment: mime4j-storage-lock.patch

This patch should resolve both problems.

In addition it adds an IllegalStateException to delete in case the MultiReferenceStorage has
already been deleted. This can only happen if a client invokes delete more than once which
is prohibited by the contract.

> Improve thread synchronization in MultiReferenceStorage
> -------------------------------------------------------
>
>                 Key: MIME4J-89
>                 URL: https://issues.apache.org/jira/browse/MIME4J-89
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Markus Wiederkehr
>             Fix For: 0.6
>
>         Attachments: mime4j-storage-lock.patch
>
>
> MultiReferenceStorage uses method based synchronization to protect the reference counting
variable.
> There are two problems with that:
> 1. storage is an interface and so storage.delete() represents a leak of the thread of
execution.
> 2. storage.delete() may be a slow operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
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