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)" <di...@incubator.apache.org> on 2005/12/05 09:03:30 UTC

[jira] Created: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Stack trace overflow when trying to connect with a bad DN
---------------------------------------------------------

         Key: DIREVE-314
         URL: http://issues.apache.org/jira/browse/DIREVE-314
     Project: Directory Server
        Type: Bug
    Reporter: Emmanuel Lecharny
    Priority: Critical
 Attachments: stackTrace.log

When trying to Bind with a bad DN, I get a StackTraceOverflow exception.

I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/DIREVE-314?page=comments#action_12359527 ] 

Emmanuel Lecharny commented on DIREVE-314:
------------------------------------------

The problem arise when the server tries to create the matchedName that will be returned in the error message. Yhis is due to the fact that the matchedName method will do a authenticate(), and as the bad DN is the principal, this authenticate() will generate an error, so a matchedName will be created, and this is of course an infinite loop ;=)

Note : I just try to do a Bind with a non existing uid. Fortunatly, we get a StackOverflowException, but the server is still alive !

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Critical
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-314?page=all ]

Emmanuel Lecharny updated DIREVE-314:
-------------------------------------

    Priority: Blocker  (was: Critical)

Raised to blocker

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Blocker
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-314?page=all ]

Emmanuel Lecharny updated DIREVE-314:
-------------------------------------

    Attachment: stackTrace.log

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Priority: Critical
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (DIRSERVER-252) Stack trace overflow when trying to connect with a bad DN

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DIRSERVER-252?page=all ]
     
Emmanuel Lecharny closed DIRSERVER-252:
---------------------------------------


I think it's fixed.

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIRSERVER-252
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-252
>      Project: Directory ApacheDS
>         Type: Bug

>     Versions: pre-1.0
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Blocker
>      Fix For: 1.0-RC1
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Assigned: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-314?page=all ]

Emmanuel Lecharny reassigned DIREVE-314:
----------------------------------------

    Assign To: Alex Karasulu

Sorry, Alex, but you are the only one who can easily fix this one ;)

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Critical
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-314?page=all ]
     
Alex Karasulu resolved DIREVE-314:
----------------------------------

    Fix Version: 1.0-RC1
     Resolution: Fixed

I think I fixed this one pretty much when doing cleanups.  I cannot reproduce it anymore.  

Committed revision 374649.

Please confirm otherwise we'll have to reopen this one.

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Blocker
>      Fix For: 1.0-RC1
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira