[ https://issues.apache.org/jira/brow...action_12499370 ]

Ole Ersoy commented on DIRSERVER-947:
-------------------------------------

Yup it's still the same exception.

I just tried it like this:

 ========================================
====================
basicAttributes.put( M_OBSOLETE,             LDAP_FALSE );
basicAttributes = new BasicAttributes(true);
basicAttributes.put( M_COLLECTIVE,           LDAP_FALSE );
 ========================================
==================================

And I get this:
javax.naming.NamingException: [LDAP: error code 80 - failed to add entry
 m-oid=1.3.6.1.4.1.18060.4.53555398.6981025.5310249.7535556.9101525.5452974.
5010152. 55710254,ou=attributeTypes,cn=das,ou=sch
ema: Unexpected exception.];
 remaining name 'm-oid=1.3.6.1.
4.1.18060.4.53555398.6981025.5310249.7535556.9101525.5452974.5010152.5571025
4'

Cheers,
- Ole



> Add an Ole Exception
> --------------------
>
>                 Key: DIRSERVER-947
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-947
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>         Environment: FC6
>            Reporter: Ole Ersoy
>            Priority: Minor
>
> I cleaned up all my tests and made everything perfect, birds singing,
> children laughing, etc.
> Just to make sure everything is tight, I run the tests
> one more time.
> I get this exception:
> javax.naming.NamingException: [LDAP: error code 80 - failed to add entry m-oid
=1.3.6.1.4.1.18060.4.55101545.5251491.1569756.3515752.5985152.5551015.5055525.501015
01.052,ou=attributeTypes,cn=das,ou=schema: Unexpected exception.]; remaining name 'm
-oid=1.
3.6.1.4.1.18060.4.55101545.5251491.1569756.3515752.5985152.5551015.5055525.50101501.052'[vbc
ol=seagreen]
> 	at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3049)
> Yeah - It's definitely unexpected.
> What's up with thiiis?
> Turns out I left one of methods like this:
>         objectClassAttribute.add( META_TOP );
> 
>         basicAttributes.put(objectClassAttribute); 
>         basicAttributes.put( M_OBSOLETE,             LDAP_FALSE );
>        ....
>        blah blah blah
> See it?  I restarted my basic attributes (And put blah blah blah right in 
the code).
> Can we have a better exception being thrown for this?
> I was thinking an Ole Exception with description "Ole, or someone pretendi
ng to be Ole, messed the code up biggg time!
> Go fix the attributes then talk to me".
> Cheers,
> - Ole[/vbcol]

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

[ Post a follow-up to this message ]