proxycache caching problem

["Dieter Kluenter" <dieter@dkluenter.de>]

Hi,
I am testing back-ldap with proxycache (HEAD and 2.3.24). Both
versions show a strange behaviour when answering substring searches
and  full searches on multiple entries.This problem has been occured in
early 2005 already, after filing an ITS it had been resolved.(can't
find the ITS reference)
On a first search all entries are displayed, on a consecutive search
only the first entry found is displayed.
The following log shows processing the NOT answered entry.

,----[ log of a query ]
| query template of incoming query = (sn=)
| Lock QC index = 1
| Not answerable: Unlock QC index=1
| QUERY NOT ANSWERABLE
| QUERY CACHEABLE
| UUID for query being added = ac013e36-8d3f-102a-8f58-9fc6a3018545
| ENTRY ADDED/MERGED, CACHED ENTRIES=0
| is_entry_objectclass("cn=xxxxx,ou=adressbuch,dc=dkluenter,dc=de", "2.5.17.0") no objectClass attribute
| is_entry_objectclass("cn=xxxxx,ou=adressbuch,dc=dkluenter,dc=de", "2.5.17.0") no objectClass attribute
| is_entry_objectclass("cn=xxxxx,ou=adressbuch,dc=dkluenter,dc=de", "1.3.6.1.4.1.4203.666.3.4") no objectClass attribute
| is_entry_objectclass("cn=xxxxx,ou=adressbuch,dc=dkluenter,dc=de", "2.16.840.1.113730.3.2.6") no objectClass attribute
| is_entry_objectclass("cn=xxxxx,ou=adressbuch,dc=dkluenter,dc=de", "2.5.17.0") no objectClass attribute
| ENTRY ADDED/MERGED, CACHED ENTRIES=0
| Added query expires at 1149997350
| Lock AQ index = 1
| TEMPLATE 1 QUERIES++ 1
| Unlock AQ index = 1 
| Base of added query = ou=adressbuch,dc=dkluenter,dc=de
| STORED QUERIES = 1
`----

When sending a SIGHUP to slapd this and all other entries are written
to id2entry.bdb and to dn2id.bdb, which can be read using strings.
Any hints?

-Dieter

-- 
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:8EF7B6C6