[DIRSERVER-1173] Delete operation with a PersistentSearch returns the deleted entry

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.2
• Fix Version/s: 2.0.0-M1
• Assignee: Kiran Ayyagari
• Reporter: Emmanuel Lécharny
• Created: 12/May/08 08:05
• Updated: 11/Jan/11 18:32
• Resolved: 28/May/10 12:45

Description

While debugging a failure in PersistentSearch I found that we have an inconsistant behavior when deleting entries :

testPsearchDelete :
ctx.destroySubcontext( RDN ); // RDN = "cn=Tori Amos"
...
assertNotNull( listener.result ); // Should be null, but is not
assertEquals( RDN, listener.result.getName() ); // Contains the deleted entry...

Another test :

testPsearchAbandon :
ctx.destroySubcontext( "cn=Jack Black" );
...
// there seems to be a race condition here
//assertNull( listener.result ); // Has been commented as otherwise, the test would fail
...

Note the comment...

While looking into the PersistentSearchListener code, here is what we have :

public void objectRemoved( NamingEvent evt )

{ // send the entry back sendEntry( evt ); }

This sendEntry method simply return the deleted entry, and is supposed to set the PersistentSearchControl, so the test is incorrect. We should test that the Control contains the correct ChangeType

Issue Links

• relates to: DIRSERVER-1153 PersistenceSearchTest fails sometimes