You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2013/06/20 12:01:22 UTC
[jira] [Updated] (DIRSERVER-1500) Error searching children of known
element.
[ https://issues.apache.org/jira/browse/DIRSERVER-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1500:
-----------------------------------------
Fix Version/s: (was: 2.0.0-RC1)
2.0.0-M13
Affects Version/s: (was: 1.5.6)
> Error searching children of known element.
> ------------------------------------------
>
> Key: DIRSERVER-1500
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1500
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.5
> Reporter: roy huang
> Assignee: Stefan Seelmann
> Fix For: 2.0.0-M13
>
> Attachments: bad.ldif
>
>
> My goal is to delete all the element per day,but occasionally it will failed for non specified element. The code will search all children elements of a node and delete it all,but may failed on this:
> NamingEnumeration ne = dirCtx.search(new LdapName(name), "objectClass=*", constraints);
> and then it throw exception.
> This problem occurred twice on 1.5.6 and 1.5.5,it affected single element,and this element can't be deleted on Apache Directory Studio too.The exception like:
> Error while reading entry
> - [LDAP: error code 80 - OTHER: failed for SearchReques
> javax.naming.NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest
> baseDn : 'ou=WLAN,ou=resource,dc=gd,dc=test,dc=com'
> filter : '(2.5.4.0=*:[121664])'
> scope : single level
> typesOnly : false
> Size Limit : 2000
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes : 'hassubordinates', 'objectclass'
> : null]; remaining name 'ou=WLAN,ou=resource,dc=gd,dc=test,dc=com'
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
> at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
> at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
> at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$1.run(JNDIConnectionWrapper.java:356)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.runAndMonitor(JNDIConnectionWrapper.java:1272)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.checkConnectionAndRunAndMonitor(JNDIConnectionWrapper.java:1203)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.search(JNDIConnectionWrapper.java:398)
> at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.search(SearchRunnable.java:500)
> at org.apache.directory.studio.ldapbrowser.core.jobs.SearchRunnable.searchAndUpdateModel(SearchRunnable.java:320)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.executeSearch(InitializeChildrenRunnable.java:361)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.initializeChildren(InitializeChildrenRunnable.java:212)
> at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeChildrenRunnable.run(InitializeChildrenRunnable.java:171)
> at org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:113)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> [LDAP: error code 80 - OTHER: failed for SearchRequest
> baseDn : 'ou=WLAN,ou=resource,dc=gd,dc=test,dc=com'
> filter : '(2.5.4.0=*:[121664])'
> scope : single level
> typesOnly : false
> Size Limit : 2000
> Time Limit : no limit
> Deref Aliases : deref Always
> attributes : 'hassubordinates', 'objectclass'
> : null]
> I upgraded 1.5.5 to 1.5.6 to avoid this bug ,but found it happened again finally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira