Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: AMQ 7.2.1.GA
Affects Version/s: AMQ 7.1.0.GA
Component/s: security
Labels:
None

Target Release:

AMQ 7.2.1.GA
Upstream Jira:
https://issues.apache.org/jira/browse/ARTEMIS-1970 https://issues.apache.org/jira/browse/ARTEMIS-1971
Steps to Reproduce:

Hide

Configure a broker to use LDAP for authenticate / authorization. Spin up a few client sessions while watching the connection count between the broker host and the LDAP provider. Kill the messaging clients and the LDAP connections remain. Spin up a few more client sessions and the LDAP connection count increases - this continues until the connection limit to the provider, file handle limit or thread limit is reached.

Show
Configure a broker to use LDAP for authenticate / authorization. Spin up a few client sessions while watching the connection count between the broker host and the LDAP provider. Kill the messaging clients and the LDAP connections remain. Spin up a few more client sessions and the LDAP connection count increases - this continues until the connection limit to the provider, file handle limit or thread limit is reached.

SFDC Cases Counter:
SFDC Cases Links:

Description

The LDAPLoginModule used in the A-MQ7 Artemis broker does not appear to support connection pooling or reuse. LDAP connections also seem to linger in an ESTABLISHED state beyond initial creation of the mesaging client session, with the result that connections pile up between the broker and the LDAP provider, eventually exhausting system resources.

Attachments

Issue Links

relates to

ENTMQBR-3604 Enabling Pooling for the LDAP Login Module Causes Shutdown to Hang

Closed

Activity

People

Assignee:: Andy Taylor

Reporter:: Duane Hawkins

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2018/07/06 9:16 AM

Updated:: 2022/03/14 5:01 AM

Resolved:: 2018/08/02 10:11 AM