[ http://issues.apache.org/jira/browse/DIRSERVER-586?page=comments#action_12425394 ] Emmanuel Lecharny commented on DIRSERVER-586: ---------------------------------------------
This problem is going wild. Ok. Let's summarize : - You are using SUN JDK 1.5.0_03 - Your are on windows - Hang just happens when you use ADS locally, and if you don't slow it down with artifacts like LdapProxy >From the last point, what I can just suspect is a synchronization problem. Let's try some more move : 1) launch your test, and when it's hanging, try to connect to ADS with LdapBrowser or JXplorer. If it does not respond, ok, this is ADS 2) give a try to the latest version of sun JVM : 1.5.0_07. There are a bunch of fixes since 1.5.0_03 (http://java.sun.com/j2se/1.5.0/ReleaseNotes.html) 3) give a try to IBM 1.5 JVM, or the latest JRockit JVM. They are both really fast. 4) A thread dump could help : client and server. On windows, I think that you can use such a tool like http://www.latenighthacking.com/projects/2003/sendSignal/ to generate stack traces, then you have other tools to analyze them. With IBM JVM, I think it's easier. On Linux, kill -3 is enough. 5) Kill a chicken, drink its blood and throw some salt on the ground, while singing under the moon. Ok, it may not help, but who knows ? Sorry that you spoiled a day to reach this conclusion : "I've dumped almost a day into this darned problem.". The positive point is that if we finally found the reason *and* the fix, then other users will benefit from yout work. What else can I say? at 1AM, nothing more, I think :( > Reliable hang of DS during query > -------------------------------- > > Key: DIRSERVER-586 > URL: http://issues.apache.org/jira/browse/DIRSERVER-586 > Project: Directory ApacheDS > Issue Type: Bug > Environment: DS 0.9.3, Windows, JDK 1.5 > Reporter: Jörg Henne > Assigned To: Alex Karasulu > Attachments: bugreport.zip, TestHang.java > > > 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
