You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2008/05/12 10:05:55 UTC
[jira] Created: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Delete operation with a PersistentSearch returns the deleted entry
------------------------------------------------------------------
Key: DIRSERVER-1173
URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
Project: Directory ApacheDS
Issue Type: Bug
Reporter: Emmanuel Lecharny
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (DIRSERVER-1173) Delete operation with a PersistentSearch returns the deleted entry
Posted by Alex Karasulu <ak...@apache.org>.
I'd push this one out to 1.5.4 where we can revamp this mechanism totally
when we switch to Cursors and be rid of the JNDIsms bogging this feature
down. Once we add more clarity without dealing with having to understand
the JNDI behavoir required by the JNDI provider this gets really easy.
Alex
On Mon, May 12, 2008 at 5:51 AM, Emmanuel Lecharny (JIRA) <ji...@apache.org>
wrote:
>
> [
> https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Emmanuel Lecharny updated DIRSERVER-1173:
> -----------------------------------------
>
> Affects Version/s: 1.5.2
> Fix Version/s: 1.5.3
>
> > Delete operation with a PersistentSearch returns the deleted entry
> > ------------------------------------------------------------------
> >
> > Key: DIRSERVER-1173
> > URL:
> https://issues.apache.org/jira/browse/DIRSERVER-1173
> > Project: Directory ApacheDS
> > Issue Type: Bug
> > Affects Versions: 1.5.2
> > Reporter: Emmanuel Lecharny
> > Fix For: 1.5.3
> >
> >
> > 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
> >
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
[jira] Updated: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1173:
-----------------------------------------
Affects Version/s: 1.5.2
Fix Version/s: 1.5.3
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.3
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1173:
-------------------------------------
These problems still showing up after rewriting all this frontend code and the event mechanism? FYI I like returning the deleted entry because it gives clients something to work with if they need to respond to a delete attempt.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.4
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari closed DIRSERVER-1173.
-------------------------------------
Resolution: Fixed
The reported problem no longer exists, closing the issue.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1173:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Fix For: 2.0.0-RC1
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626353#action_12626353 ]
Emmanuel Lecharny commented on DIRSERVER-1173:
----------------------------------------------
I still have the very same failure ...
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.4
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1173:
-----------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.4
Potsponed. The failing test has been commented.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.4
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari reassigned DIRSERVER-1173:
-----------------------------------------
Assignee: Kiran Ayyagari (was: Alex Karasulu)
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804992#action_12804992 ]
Kiran Ayyagari commented on DIRSERVER-1173:
-------------------------------------------
is anyone seeing this problem with PSearch now?
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Fix For: 2.0.0-RC1
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-1173:
----------------------------------------
Assignee: Alex Karasulu
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Fix For: 1.5.5
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626288#action_12626288 ]
Emmanuel Lecharny commented on DIRSERVER-1173:
----------------------------------------------
I have to check the test, and run it against the trunk.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Fix For: 1.5.4
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596020#action_12596020 ]
Emmanuel Lecharny commented on DIRSERVER-1173:
----------------------------------------------
Actually, it's even worse...
The testPsearchAbandon is not consistent at all. Sometime it fails, sometime it succeeds.
It seems that when it fails, an AbandonRequest is received _before_ the modify request is run, leading to a removal of the PersistentSearch handler.
Depending on which test is run before the testPsearchAbandon, the result may be different.
I suggest either we fix it in 1.5.3, or we remove the tests and consider PersistentSearch broken and to be fixed in 1.5.4, but in the mean time, the tests should be commented.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Emmanuel Lecharny
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1173) Delete operation with a
PersistentSearch returns the deleted entry
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1173:
-------------------------------------
Fix Version/s: (was: 1.5.4)
1.5.5
Postponing.
> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1173
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Fix For: 1.5.5
>
>
> 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
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.