You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2012/07/30 11:22:34 UTC
[jira] [Created] (AMQ-3951) LDAP Connection Timeouts in
CachedLDAPAuthorizationMAp
David Valeri created AMQ-3951:
---------------------------------
Summary: LDAP Connection Timeouts in CachedLDAPAuthorizationMAp
Key: AMQ-3951
URL: https://issues.apache.org/jira/browse/AMQ-3951
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Reporter: David Valeri
Fix For: 5.7.0
The LDAP connection is cached. When no using push based updates, the LDAP server may drop the connection to the broker. In this situation, the next scheduled polling cycle will not be able to connect to the LDAP server.
Update the polling based solution to leverage a new connection on each refresh.
--
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
[jira] [Closed] (AMQ-3951) LDAP Connection Timeouts in
CachedLDAPAuthorizationMap
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri closed AMQ-3951.
-----------------------------
Resolution: Duplicate
Didn't catch the duplicate issue until I went to fix the code. Resolved in AMQ-3845.
> LDAP Connection Timeouts in CachedLDAPAuthorizationMap
> ------------------------------------------------------
>
> Key: AMQ-3951
> URL: https://issues.apache.org/jira/browse/AMQ-3951
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Reporter: David Valeri
> Fix For: 5.7.0
>
>
> The LDAP connection is cached. When no using push based updates, the LDAP server may drop the connection to the broker. In this situation, the next scheduled polling cycle will not be able to connect to the LDAP server.
> Update the polling based solution to leverage a new connection on each refresh.
--
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
[jira] [Updated] (AMQ-3951) LDAP Connection Timeouts in
CachedLDAPAuthorizationMap
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri updated AMQ-3951:
------------------------------
Summary: LDAP Connection Timeouts in CachedLDAPAuthorizationMap (was: LDAP Connection Timeouts in CachedLDAPAuthorizationMAp)
> LDAP Connection Timeouts in CachedLDAPAuthorizationMap
> ------------------------------------------------------
>
> Key: AMQ-3951
> URL: https://issues.apache.org/jira/browse/AMQ-3951
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Reporter: David Valeri
> Fix For: 5.7.0
>
>
> The LDAP connection is cached. When no using push based updates, the LDAP server may drop the connection to the broker. In this situation, the next scheduled polling cycle will not be able to connect to the LDAP server.
> Update the polling based solution to leverage a new connection on each refresh.
--
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