Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 7
Affects Version/s: 5.0u11
Component/s: core-libs
Labels:
- noreg-hard
- verify-waive-setup

Subcomponent:
javax.naming
Resolved In Build:
b134
CPU:

generic
OS:

generic
Verification:
Not verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2208809	6u27	Sean Coffey	P3	Closed	Fixed	b01
JDK-2208660	6u26-rev	Sean Coffey	P3	Resolved	Fixed	b21
JDK-2208640	6u25-rev	Sean Coffey	P3	Resolved	Fixed	b21
JDK-2171516	6u24-rev	Sean Coffey	P3	Closed	Fixed	b25
JDK-2178182	5.0u21	Sean Coffey	P3	Resolved	Fixed	b01
JDK-2179650	5.0u20-rev	Sean Coffey	P3	Closed	Fixed	b03
JDK-2171517	5.0u19-rev	Sean Coffey	P3	Resolved	Fixed	b03

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.

backported by

JDK-2171517 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Resolved

JDK-2178182 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Resolved

JDK-2208640 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Resolved

JDK-2208660 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Resolved

JDK-2171516 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Closed

JDK-2179650 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Closed

JDK-2208809 Very large LDAP requests throw a OOM on LDAP servers which aren't aware of Paged Results Controls

Closed

relates to

JDK-6862356 7 ldap jndi tests fail with 5.0u20-rev-b03, but pass with 5.0u20 b02 SSR

Closed

JDK-6874156 7 ldap jndi tests fail with 5.0u22 b01

Closed

JDK-6747875 Very Large LDAP requests/responses can lead to an OutOfMemoryError

Closed

(2 backported by, 3 relates to)

Assignee:: Sean Coffey

Reporter:: Johann Löfflmann (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2008-09-19 04:50

Updated:: 2017-05-16 16:33

Resolved:: 2011-05-17 19:49

Imported:: 16/Sep/12 7:57 PM

Indexed:: 18/Jul/12 2:23 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates