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 "Steve Brewin (Created) (JIRA)" <se...@james.apache.org> on 2011/12/05 19:44:41 UTC
[jira] [Created] (JAMES-1352) Increase the robustness of
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
Increase the robustness of org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
---------------------------------------------------------------------------------
Key: JAMES-1352
URL: https://issues.apache.org/jira/browse/JAMES-1352
Project: JAMES Server
Issue Type: Improvement
Components: UsersStore & UsersRepository
Affects Versions: 3.0-beta3
Reporter: Steve Brewin
Assignee: Steve Brewin
Priority: Minor
Fix For: Trunk
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository obtains its connection to the LDAP repository during init() processing and thereafter assumes it to be valid. When, as may sometimes temporarily or permanently occur, the connection becomes invalid the resulting javax.naming.CommunicationException is propogated to the caller and no attempt is made to reestablish the connection. James must be restarted to reestablish the connection, which is likely to be unacceptable in a production environment.
To correct this, org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository needs to be modified in the following ways:
1) Make the connection timeout period configurable
2) Introduce the ability to attempt to reinstate and retry connections a configurable number of times with a configurable delay between retries when recoverable exception is thrown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.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-1352) Increase the robustness of
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
Posted by "Steve Brewin (Resolved) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Brewin resolved JAMES-1352.
---------------------------------
Resolution: Fixed
> Increase the robustness of org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
> ---------------------------------------------------------------------------------
>
> Key: JAMES-1352
> URL: https://issues.apache.org/jira/browse/JAMES-1352
> Project: JAMES Server
> Issue Type: Improvement
> Components: UsersStore & UsersRepository
> Affects Versions: 3.0-beta3
> Reporter: Steve Brewin
> Assignee: Steve Brewin
> Priority: Minor
> Fix For: Trunk
>
>
> org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository obtains its connection to the LDAP repository during init() processing and thereafter assumes it to be valid. When, as may sometimes temporarily or permanently occur, the connection becomes invalid the resulting javax.naming.CommunicationException is propogated to the caller and no attempt is made to reestablish the connection. James must be restarted to reestablish the connection, which is likely to be unacceptable in a production environment.
> To correct this, org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository needs to be modified in the following ways:
> 1) Make the connection timeout period configurable
> 2) Introduce the ability to attempt to reinstate and retry connections a configurable number of times with a configurable delay between retries when a recoverable exception is thrown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.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-1352) Increase the robustness of
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
Posted by "Steve Brewin (Updated) (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Brewin updated JAMES-1352:
--------------------------------
Description:
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository obtains its connection to the LDAP repository during init() processing and thereafter assumes it to be valid. When, as may sometimes temporarily or permanently occur, the connection becomes invalid the resulting javax.naming.CommunicationException is propogated to the caller and no attempt is made to reestablish the connection. James must be restarted to reestablish the connection, which is likely to be unacceptable in a production environment.
To correct this, org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository needs to be modified in the following ways:
1) Make the connection timeout period configurable
2) Introduce the ability to attempt to reinstate and retry connections a configurable number of times with a configurable delay between retries when a recoverable exception is thrown
was:
org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository obtains its connection to the LDAP repository during init() processing and thereafter assumes it to be valid. When, as may sometimes temporarily or permanently occur, the connection becomes invalid the resulting javax.naming.CommunicationException is propogated to the caller and no attempt is made to reestablish the connection. James must be restarted to reestablish the connection, which is likely to be unacceptable in a production environment.
To correct this, org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository needs to be modified in the following ways:
1) Make the connection timeout period configurable
2) Introduce the ability to attempt to reinstate and retry connections a configurable number of times with a configurable delay between retries when recoverable exception is thrown
> Increase the robustness of org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository
> ---------------------------------------------------------------------------------
>
> Key: JAMES-1352
> URL: https://issues.apache.org/jira/browse/JAMES-1352
> Project: JAMES Server
> Issue Type: Improvement
> Components: UsersStore & UsersRepository
> Affects Versions: 3.0-beta3
> Reporter: Steve Brewin
> Assignee: Steve Brewin
> Priority: Minor
> Fix For: Trunk
>
>
> org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository obtains its connection to the LDAP repository during init() processing and thereafter assumes it to be valid. When, as may sometimes temporarily or permanently occur, the connection becomes invalid the resulting javax.naming.CommunicationException is propogated to the caller and no attempt is made to reestablish the connection. James must be restarted to reestablish the connection, which is likely to be unacceptable in a production environment.
> To correct this, org.apache.james.user.ldap.ReadOnlyUsersLDAPRepository needs to be modified in the following ways:
> 1) Make the connection timeout period configurable
> 2) Introduce the ability to attempt to reinstate and retry connections a configurable number of times with a configurable delay between retries when a recoverable exception is thrown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.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