[jboss-jira] [JBoss JIRA] Closed: (JBMAIL-130) clusterize locks table

[Andrew Oliver (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMAIL-130?page=all ]

Andrew Oliver closed JBMAIL-130.
--------------------------------

    Fix Version/s:     (was: 1.0-RC1)
       Resolution: Won't Fix
         Assignee:     (was: Andrew Oliver)

> clusterize locks table
> ----------------------
>
>                 Key: JBMAIL-130
>                 URL: http://jira.jboss.com/jira/browse/JBMAIL-130
>             Project: JBoss Mail ** Closed - moved to http://buni.org **
>          Issue Type: Feature Request
>          Components: POP
>    Affects Versions: 1.0-RC1
>            Reporter: Andrew Oliver
>
> Locks table needs to have some kind of instance id and the thread id.  Locks should be deleted or at runtime if they are from the same instance upon startup and if that thread is known to be gone and from the owning instance.  Meaning if server A owns the lock and the same user connects to server A, server A can check the thread pool and see if the same thread ID is still in existence with the same userID. . . IF not then the lock can be safely ignored/deleted.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira