You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Jörg Henne (JIRA)" <ji...@apache.org> on 2006/06/30 01:29:31 UTC

[jira] Updated: (DIRSERVER-586) Reliable hang of DS during query

     [ http://issues.apache.org/jira/browse/DIRSERVER-586?page=all ]

Jörg Henne updated DIRSERVER-586:
---------------------------------

    Attachment: TestHang.java

The test cases

> Reliable hang of DS during query
> --------------------------------
>
>          Key: DIRSERVER-586
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-586
>      Project: Directory ApacheDS
>         Type: Bug

>  Environment: DS 0.9.3, Windows, JDK 1.5
>     Reporter: Jörg Henne
>     Assignee: Alex Karasulu
>  Attachments: TestHang.java, bugreport.zip
>
> When running the attached test, the directory server hangs after executing a slew of operations when searching for objects.
> First of all, some background on the test case:
> The attached test case (in the form of an exported eclipse project) is, unfortunately, based on quite a few classes. They are part of a project I am currently working on: an object to ldap mapper with a similar approach as castor for XML or hibernate for RDBMS, albeit a lot more modest in complexity (I'll, hopefully, one day be able to open-source it - for now it is still much to immature). I have supplied all that stuff mainly for your reference.
> To run the test case, please make sure that the constant "URL" in LDAPDirectoryTest points to a valid directory. The URL the context points to must exist. It will, however, subsequently create lots of nodes below it.
> The hang seems to be related to some kind of deadlock, since it doesn't occur once the whole test is run via a single context only. To achieve this, set the constant "ONE_CONTEXT" to true (each LDAPDirectory uses its own set of contexts).
> If you have any problems running the test, please don't hesitate to contact me.

-- 
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