directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Smith (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-430) NullPointer exception when fetching children of a node
Date Thu, 27 Nov 2008 09:57:47 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651308#action_12651308
] 

Richard Smith commented on DIRSTUDIO-430:
-----------------------------------------

No,

ApacheDS does not handle the error returned by JDNI correctly.

Apologies, yesterday was a bad day for communication. Brain was disengaged.

Luma and GQ both report the error in their respective error handlers and display the error
returned by the server (translated from ASN.1 into (l)user speak) "Invalid DN" which I believe
is LDAP error 0x22 (LDAP_INVALID_DN_SYNTAX)

ApacheDS only displays a NullPointerException and no detail on the reason behind the NullPointer[1]
a bit unfriendly and amazingly frustrating.

[1] It does this in several places, although the above bug is the straw that broke the camels
back so to speak, since the rest of the time I just work around it, having little to no time
to work out what the hell is going on. 

> NullPointer exception when fetching children of a node
> ------------------------------------------------------
>
>                 Key: DIRSTUDIO-430
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-430
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.3.0
>         Environment: Desktop: Ubuntu 8.10, Linux 2.6, Java 6 (standard packages)
> Server: Ubuntu 8.04, Linux 2.6, OpenLDAP 2.3 (standard packages)
>            Reporter: Richard Smith
>
> When I browse to a specific node in my directory I get the following exception.
> Error while reading entry
> java.lang.NullPointerException
>   java.lang.NullPointerException
> Ldif of the branch in question (some info removed):
> dn: ou=principals,o=directory
> objectClass: organizationalUnit
> objectClass: top
> ou: principals
> dn: krb5PrincipalName=krbtgt/KERBEROSDOMAIN@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: krbtgt/KERBEROSDOMAIN
> dn: krb5PrincipalName=kadmin/changepw@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: kadmin/changepw
> dn: krb5PrincipalName=kadmin/admin@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: kadmin/admin
> dn: krb5PrincipalName=changepw/kerberos@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: changepw/kerberos
> dn: krb5PrincipalName=kadmin/hprop@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: kadmin/hprop
> dn: krb5PrincipalName=default@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: default
> dn: krb5PrincipalName=richard@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> objectClass: shadowAccount
> uid: richard
> userPassword:: aG50bWhhdm5iIQ==
> dn: krb5PrincipalName=ldap/pinkfloyd.KERBEROSDOMAIN@KERBEROSDOMAIN,ou=principals,o=directory
> objectClass: top
> objectClass: account
> objectClass: krb5Principal
> objectClass: krb5KDCEntry
> uid: ldap/pinkfloyd.KERBEROSDOMAIN

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


Mime
View raw message