Here's the customer's report:
Date: Thu, 4 Oct 2001 15:44:02 -0400
From: Jay Boyd <###@###.###>
Subject: NamingEnumeration.close() causing ABANDON msg on iPlanet 5.0
To: ###@###.###

I'm seeing some curious behavior on iPlanet 5.0 accessing it from JNDI
(1.3.1). I'm seeing ABANDON messages in the iPlanet access log and have
narrowed the cause down to these two conditions:

1. Closing a Search()'s NamingEnumeration before all the results have been
enumerated (i.e., NamingEnumeration.close())

2. Performing multiple searches on the same DirContext and for each search,
never enumerating through all the results and not explicitly performing a
close on each enumeration. Here I believe GC is probably eventually causing
the close.

I don't believe the close is causing an abnormal condition, but I can't
imagine why else it would be logged. For both of these searches I'm using a
search scope of OBJECT_SCOPE so I have no reason to perform a second next()
operation on the NamingEnumeration. If I do enumerate through each
NamingEnumeration until hasMore() returns false, I don't get the ABANDON
msg. I am not using any paging controls on the server.

I have some customers that scrutinize access logs and I'm certain I'll need
to explain this in the future. I'll try the iPlanet folks if no one has any
thoughts...

- Jay