[
https://issues.apache.org/jira/browse/DIRSERVER-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-938.
-----------------------------------------
Resolution: Fixed
It seems that the test is not failing anymore. My guess is that the fix applied
by Alex yesterday, related to the ThreadPool and the Filter parsing bad
reinitialization, fixed it too.
I have replayed the very same program this morning, after having svn up the
code, and it's all ok...
> duplicate entries possible as well as null pointer on search using custom
> schema attribute in search filter
> -----------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-938
> URL: https://issues.apache.org/jira/browse/DIRSERVER-938
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: windows
> Reporter: Brian Gadwell
> Assignee: Emmanuel Lecharny
> Fix For: 1.5.1
>
> Attachments: DirectoryBug.java
>
>
> Run the attached test application with an empty working directory and no
> program argument to reproduce the duplicate entry bug.
> Run the attached test application with an empty working directory and a
> single program argument (can be whatever) to reproduce the null pointer on
> search using custom schema attribute in search filter bug.
> Each test has 2 parts one before the directory shutdown code being run and
> one after. The app does the directory restart programatically to easily
> demonstrate the bug, but if you were to manually do the restart and not allow
> the shutdown code to be run then bith bugs are not reproducable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
