|
Quick Lists
|
|
Bug ID:
|
6750362
|
|
Votes
|
0
|
|
Synopsis
|
Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls
|
|
Category
|
jndi:ldap
|
|
Reported Against
|
|
|
Release Fixed
|
|
|
State
|
1-Dispatched,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6747875
|
|
Submit Date
|
19-SEP-2008
|
|
Description
|
In CR 6747875 we have documented that if an LDAP server responds with many thousands of entries, a client could stop with an "java.lang.OutOfMemoryError: Java heap space" if the request results cannot be processed fast enough. The feature called Paged Results Control has been suggested in order to control the rate of arrival of LDAP results. However, this approach doesn't work with each LDAP server.
This request is to improve the actual jndi producer/consumer implementation in order to make it working even if a LDAP server don't support the Paged Results Control feature.
A testcase is attached to the CR.
Posted Date : 2008-09-19 11:50:01.0
|
|
Work Around
|
1) Buy more memory, use a 64 bit JVM and increase the Java heap until it works.
Note that this workaround isn't suitable for many customer.
2) Use a LDAP server which supports Paged Results Controls. See also
http://java.sun.com/j2se/1.5.0/docs/api/javax/naming/ldap/PagedResultsControl.html
Note that this workaround isn't suitable for the customer, as the customer want to support LDAP servers even if they don't have that feature.
|
|
Evaluation
|
N/A
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
