Apache Directory Project - [jira] Commented: (DIRSERVER-586) Reliable hang of DS during query

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > August 2006 > [jira] Commented: (DIRSERVER-586) Reliable hang of DS during query





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (DIRSERVER-586) Reliable hang of DS during query
Trustin Lee (JIRA)

2006-08-31, 7:11 am

[ http://issues.apache.org/jira/brows...=3Dcomments#ac=
tion_12431848 ]=20
=20
Trustin Lee commented on DIRSERVER-586:
---------------------------------------

I loaded the attached bugreport project in my eclipse workbench and ran the=
tests including TestHang.java. The tests don't hang but they prints out=
some errors:

INFO 2006-08-31 18:49:56,533 [ldap.Mapping; main]: LDAP mapping initialize=
d
DEBUG 2006-08-31 18:49:56,536 [ldap.Mapping; main]: load(): type=3Dclass co=
m.levigo.tcat.common.model.OrganizationalUnit, ctx=3Djavax.naming.directory=
..InitialDirContext@2c1e6b, dn=3Dou=3Dappgroups
DEBUG 2006-08-31 18:49:56,537 [ldap.TypeMapping; main]: loading object of c=
lass com.levigo.tcat.common.model.OrganizationalUnit for dn=3Dou=3Dappgroup=
s
DEBUG 2006-08-31 18:49:56,537 [ldap.Mapping; main]: create(): create=3Dclas=
s com.levigo.tcat.common.model.OrganizationalUnit
DEBUG 2006-08-31 18:49:56,538 [ldap.Mapping; main]: save(): object=3Dcom.le=
vigo.tcat.common.model.OrganizationalUnit@811c88, ctx=3Djavax.naming.direct=
ory.InitialDirContext@2c1e6b, baseDN=3D
DEBUG 2006-08-31 18:49:56,538 [ldap.AttributeMapping; main]: dehydrating ob=
ject of type class com.levigo.tcat.common.model.OrganizationalUnit
DEBUG 2006-08-31 18:49:56,539 [ldap.AttributeMapping; main]: dehydrating ob=
ject of type class com.levigo.tcat.common.model.OrganizationalUnit
DEBUG 2006-08-31 18:49:56,543 [ldap.Mapping; main]: list(): type=3Dclass co=
m.levigo.tcat.common.model.Client, ctx=3Dnull, filter=3Dnull, searchBase=3D=
null
DEBUG 2006-08-31 18:49:56,546 [ldap.TypeMapping; main]: listing objects of =
class com.levigo.tcat.common.model.Client for base=3Dou=3Dclients, filter=
=3Dnull
com.levigo.tcat.common.directory.DirectoryException: Can't save object
=09at com.levigo.tcat.common.directory.ldap.TypeMapping.save(TypeMapping.ja=
va:354)
=09at com.levigo.tcat.common.directory.ldap.Mapping.save(Mapping.java:173)
=09at com.levigo.tcat.common.directory.ldap.LDAPDirectory.setupBaseStructur=
e(LDAPDirectory.java:116)
=09at com.levigo.tcat.common.directory.ldap.LDAPDirectory.<init>(LDAPDirect=
ory.java:88)
=09at LDAPDirectoryTest.getDirectory(LDAPDirectoryTest.java:34)
=09at LDAPDirectoryTest.setUp(LDAPDirectoryTest.java:42)
=09at junit.framework.TestCase.runBare(TestCase.java:125)
=09at junit.framework.TestResult$1.protect(TestResult.java:106)
=09at junit.framework.TestResult.runProtected(TestResult.java:124)
=09at junit.framework.TestResult.run(TestResult.java:109)
=09at junit.framework.TestCase.run(TestCase.java:118)
=09at junit.framework.TestSuite.runTest(TestSuite.java:208)
=09at junit.framework.TestSuite.run(TestSuite.java:203)
=09at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(=
JUnit3TestReference.java:128)
=09at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution=
..java:38)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remot=
eTestRunner.java:460)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remot=
eTestRunner.java:673)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTest=
Runner.java:386)
=09at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTes=
tRunner.java:196)
Caused by: com.levigo.tcat.common.directory.DirectoryException: Can't marsh=
al instance of class com.levigo.tcat.common.model.OrganizationalUnit
=09at com.levigo.tcat.common.directory.ldap.TypeMapping.saveNewObject(TypeM=
apping.java:393)
=09at com.levigo.tcat.common.directory.ldap.TypeMapping.save(TypeMapping.ja=
va:352)
=09... 18 more
Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 5=
3 - no global superior knowledge]; remaining name 'ou=3Dappgroups'
=09at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3058)
=09at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
=09at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
=09at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:770)
=09at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(Compo=
nentDirContext.java:319)
=09at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(=
PartialCompositeDirContext.java:248)
=09at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirC=
ontext.java:183)
=09at com.levigo.tcat.common.directory.ldap.TypeMapping.saveNewObject(TypeM=
apping.java:374)
=09... 19 more

Any clue?

> 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=C3=B6rg Henne
> Assigned To: Emmanuel Lecharny
> Attachments: bugreport.zip, TestHang.java
>
>
> When running the attached test, the directory server hangs after executin=

g 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, u=

nfortunately, 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 complexi=
ty (I'll, hopefully, one day be able to open-source it - for now it is stil=
l much to immature). I have supplied all that stuff mainly for your referen=
ce.
> To run the test case, please make sure that the constant "URL" in LDAPDir=

ectoryTest 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 o=

ccur 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 se=
t of contexts).
> If you have any problems running the test, please don't hesitate to conta=

ct me.

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



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com