This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

LDAP number of connection exceeded from defined limit and connection unavailablePage Title Module

we observed two issues as follows:
1. Connection lost issue with exceeded number of connections size from the defined maximum number of connection pool size.
2. Unavailable: Failed to borrow DirContext from pool.; nested exception is java.util.NoSuchElementException: Timeout waiting for idle object. Ongoing transaction aborted.

Logs of both issues attached with LDAP context settings.

Please help me and let me know if any configured parameters tuning will resolve the issue or is a known issue which resolved by upgrading any component.

Here we are suspecting concurrent transaction management issue of commons pool which exceeded pool size than defined limit and in another case ongoing transaction of a connection aborted during that concurrent transaction load time.

So we are in a plan to upgrade Apache Commons Pool 1.5.4 to latest version 1.6. Expecting this pool issue resolved in the latest release one.

Please let me have your kind guidances to be in right track for the issue resolutions.