directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-1357) NullPointerException when deleting alias
Date Tue, 26 May 2009 22:24:45 GMT


Emmanuel Lecharny commented on DIRSERVER-1357:

I can fix the NPE, but then I have another issue.

Let's say we have the entry E, and the alias A pointing on E. 
1) We remove E. A is pointing on nothing, the alias index is updated
2) We now remove A

So far, so good, the test pass ok. Now we have to revert the operation :
3) we inject A back into the server : BANG !

The server does not allow addition of aliases pointing on invalid entries  :
         * Check For Target Existance
         * We do not allow the creation of inconsistant aliases.  Aliases should
         * not be broken links.  If the target does not exist we start screaming

I'm not sure this is a correct behavior. All in all, it's the client responsability to manage
correctly Aliases, no ?

> NullPointerException when deleting alias
> ----------------------------------------
>                 Key: DIRSERVER-1357
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.5.5, 1.5.4
>            Reporter: Stefan Seelmann
>             Fix For: 1.5.5
>         Attachments:
> There is a NPE when deleting an alias entry is some special case. Here is a example DIT:
> ou=system
>    |--ou=sales
>    |    |--cn=foo  <--real entry
>    |--ou=engineering
>         |--cn=foo  <--alias, pointing to the real entry
> When I first delete the real entry and afterwards the alias the server throws an exception,
when it cleans the oneAliasIdx and subAliasIdx in the JdbmStore. Note, the exception does
not occur if the real entry and alias are direct descendants of the context entry, because
in that case the oneAliasIdx and subAliasIdx are not used.
> java.lang.NullPointerException
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message