You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2006/05/19 16:54:29 UTC
[jira] Created: (JAMES-504) RemoteDelivery threads do not unlock
delayed mails
RemoteDelivery threads do not unlock delayed mails
--------------------------------------------------
Key: JAMES-504
URL: http://issues.apache.org/jira/browse/JAMES-504
Project: James
Type: Bug
Versions: 2.3.0a2, 2.2.0
Reporter: Stefano Bagnara
Assigned to: Stefano Bagnara
Fix For: 2.4.0
The problem is that after a failed temporary attempt, only the thread that made the first attempt will be able to make further attempts because it never unlock the message.
We already fixed this in trunk, it should be backported to 2.3
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-504) RemoteDelivery threads do not unlock
delayed mails
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-504?page=all ]
Stefano Bagnara updated JAMES-504:
----------------------------------
Fix Version/s: (was: 3.0)
> RemoteDelivery threads do not unlock delayed mails
> --------------------------------------------------
>
> Key: JAMES-504
> URL: http://issues.apache.org/jira/browse/JAMES-504
> Project: James
> Issue Type: Bug
> Affects Versions: 2.2.0, 2.3.0a2
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Fix For: 2.3.0a3
>
>
> The problem is that after a failed temporary attempt, only the thread that made the first attempt will be able to make further attempts because it never unlock the message.
> We already fixed this in trunk, it should be backported to 2.3
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-504) RemoteDelivery threads do not unlock
delayed mails
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-504?page=all ]
Stefano Bagnara resolved JAMES-504:
-----------------------------------
Fix Version: 2.3.0a3
Resolution: Fixed
Backported to 2.3 branch
> RemoteDelivery threads do not unlock delayed mails
> --------------------------------------------------
>
> Key: JAMES-504
> URL: http://issues.apache.org/jira/browse/JAMES-504
> Project: James
> Type: Bug
> Versions: 2.3.0a2, 2.2.0
> Reporter: Stefano Bagnara
> Assignee: Stefano Bagnara
> Fix For: 2.3.0a3, 2.4.0
>
> The problem is that after a failed temporary attempt, only the thread that made the first attempt will be able to make further attempts because it never unlock the message.
> We already fixed this in trunk, it should be backported to 2.3
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org