directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-177) Bad filter makes filter parser hang rather than throw an exception
Date Sat, 15 Apr 2006 13:22:01 GMT
    [ ] 

Stefan Zoerner commented on DIRSERVER-177:

Is it possible to get more info on this? 

Within my test cases, I have some search operations here:
The class contains a test method testFiltersWithSyntaxErrors which expects an InvalidSearchFilterException
in case of a filter like "This is no filter" or "blah". It works as expected for RC1, but
it seems to me that it is the JNDI provider for LDAP on the client side causing the exception
(no ApacheDS involved). 

How was the error achieved in detail? What does "try simple malformed filter" exactly means?
command line tool like ldapsearch?

> Bad filter makes filter parser hang rather than throw an exception
> ------------------------------------------------------------------
>          Key: DIRSERVER-177
>          URL:
>      Project: Directory ApacheDS
>         Type: Bug

>   Components: ldap
>     Reporter: Alex Karasulu

> try simple malformed filter like 'blah' and see what happends: 
> line 1:1: expecting LPAREN, found 'blah' 
> This is printed out to system.err and no exception results.  This is not good because
it can hang indefinately.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message