You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2007/02/15 20:34:05 UTC
[jira] Created: (DIRSERVER-856) Connecting to ApacheDS with
Softerra LDAP Administrator fails
Connecting to ApacheDS with Softerra LDAP Administrator fails
-------------------------------------------------------------
Key: DIRSERVER-856
URL: https://issues.apache.org/jira/browse/DIRSERVER-856
Project: Directory ApacheDS
Issue Type: Bug
Environment: * ApacheDS 1.0.1 (SNAPSHOT, Rev. Rev. 507868)
* Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
* Windows XP Professional SP2
* Softerra LDAP Administrator v.3.4 (build 1700)
Reporter: Stefan Zoerner
Priority: Critical
Fix For: 1.0.1
Trying to connect to ApacheDS with Softerra LDAP Administrator fails. The tool states that schema loading failed, and refuses to browse the directory at all afterwards.
Other tools are able to read the schema and connect, for instance JXplorer.
In order to investigate the problem further, I found out that some JNDI operations, which try to fetch the schema, have problems as well. I'll attach a suitable JUnit test for that soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-856) Connecting to ApacheDS with Softerra
LDAP Administrator fails
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner closed DIRSERVER-856.
------------------------------------
I confirm that rev. 508131 works perfectly with Softerra LDAP Administrator 3.4. Problem with schema fetching has vanished.
Well done, Emmanuel!
> Connecting to ApacheDS with Softerra LDAP Administrator fails
> -------------------------------------------------------------
>
> Key: DIRSERVER-856
> URL: https://issues.apache.org/jira/browse/DIRSERVER-856
> Project: Directory ApacheDS
> Issue Type: Bug
> Environment: * ApacheDS 1.0.1 (SNAPSHOT, Rev. Rev. 507868)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> * Softerra LDAP Administrator v.3.4 (build 1700)
> Reporter: Stefan Zoerner
> Priority: Critical
> Fix For: 1.0.1
>
> Attachments: FetchSchemaTest.java
>
>
> Trying to connect to ApacheDS with Softerra LDAP Administrator fails. The tool states that schema loading failed, and refuses to browse the directory at all afterwards.
> Other tools are able to read the schema and connect, for instance JXplorer.
> In order to investigate the problem further, I found out that some JNDI operations, which try to fetch the schema, have problems as well. I'll attach a suitable JUnit test for that soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-856) Connecting to ApacheDS with
Softerra LDAP Administrator fails
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSERVER-856:
-------------------------------------
Attachment: FetchSchemaTest.java
The following JUnit test tries to fetch schema details from an up and running ApacheDS with default server.xml with the help of JNDI.
It passes on
* Sun Java System Directory Server 5.2
* IBM Tivoli Directory Server 6.0
* OpenLDAP 2.3
On the current ApacheDS 1.0 branch, it fails with the stack trace below
javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - failed on search operation: The attribute javaRemoteLocation was not recognized as a valid attributeType.:
SearchRequest
baseDn : 'cn=schema,ou=system'
filter : '(2.5.4.0=subschema) '
scope : base object
typesOnly : false
no limit
Time Limit : no limit
Deref Aliases : deref Always
attributes : 'javaRemoteLocation', 'javaSerializedData', 'objectClass', 'matchingRules', 'javaClassName', 'javaCodeBase', 'attributeTypes', 'javaClassNames', 'objectClasses', 'javaReferenceAddress', 'javaFactory', 'ldapSyntaxes'
:
org.apache.directory.shared.ldap.exception.LdapInvalidAttributeIdentifierException: The attribute javaRemoteLocation was not recognized as a valid attributeType.
at org.apache.directory.server.core.schema.SchemaService.filterAttributesToReturn(SchemaService.java:407)
at org.apache.directory.server.core.schema.SchemaService.search(SchemaService.java:442)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.exception.ExceptionService.search(ExceptionService.java:389)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.authz.DefaultAuthorizationService.search(DefaultAuthorizationService.java:495)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.authz.AuthorizationService.search(AuthorizationService.java:978)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.referral.ReferralService.search(ReferralService.java:1005)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.authn.AuthenticationService.search(AuthenticationService.java:417)
at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.search(InterceptorChain.java:1263)
at org.apache.directory.server.core.normalization.NormalizationService.search(NormalizationService.java:326)
at org.apache.directory.server.core.interceptor.InterceptorChain.search(InterceptorChain.java:828)
at org.apache.directory.server.core.partition.PartitionNexusProxy.search(PartitionNexusProxy.java:478)
at org.apache.directory.server.core.partition.PartitionNexusProxy.search(PartitionNexusProxy.java:423)
at org.apache.directory.server.core.jndi.ServerDirContext.search(ServerDirContext.java:609)
at org.apache.directory.server.ldap.support.SearchHandler.messageReceived(SearchHandler.java:313)
at org.apache.mina.handler.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:144)
at org.apache.directory.server.ldap.LdapProtocolProvider$LdapProtocolHandler.messageReceived(LdapProtocolProvider.java:403)
at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived(AbstractIoFilterChain.java:703)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimpleProtocolDecoderOutput.java:60)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:184)
at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:362)
at org.apache.mina.common.support.AbstractIoFilterChain.access$1200(AbstractIoFilterChain.java:54)
at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:800)
at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:243)
at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:305)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Unknown Source)
]; remaining name ''
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.buildSchemaTree(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.getSchemaTree(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_getSchema(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getSchema(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getSchema(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getSchema(Unknown Source)
at javax.naming.directory.InitialDirContext.getSchema(Unknown Source)
at schema.FetchSchemaTest.testFetchClasses(FetchSchemaTest.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
> Connecting to ApacheDS with Softerra LDAP Administrator fails
> -------------------------------------------------------------
>
> Key: DIRSERVER-856
> URL: https://issues.apache.org/jira/browse/DIRSERVER-856
> Project: Directory ApacheDS
> Issue Type: Bug
> Environment: * ApacheDS 1.0.1 (SNAPSHOT, Rev. Rev. 507868)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> * Softerra LDAP Administrator v.3.4 (build 1700)
> Reporter: Stefan Zoerner
> Priority: Critical
> Fix For: 1.0.1
>
> Attachments: FetchSchemaTest.java
>
>
> Trying to connect to ApacheDS with Softerra LDAP Administrator fails. The tool states that schema loading failed, and refuses to browse the directory at all afterwards.
> Other tools are able to read the schema and connect, for instance JXplorer.
> In order to investigate the problem further, I found out that some JNDI operations, which try to fetch the schema, have problems as well. I'll attach a suitable JUnit test for that soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-856) Connecting to ApacheDS with
Softerra LDAP Administrator fails
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-856.
-----------------------------------------
Resolution: Duplicate
Was the same problem than DIRSERVER-836
> Connecting to ApacheDS with Softerra LDAP Administrator fails
> -------------------------------------------------------------
>
> Key: DIRSERVER-856
> URL: https://issues.apache.org/jira/browse/DIRSERVER-856
> Project: Directory ApacheDS
> Issue Type: Bug
> Environment: * ApacheDS 1.0.1 (SNAPSHOT, Rev. Rev. 507868)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> * Softerra LDAP Administrator v.3.4 (build 1700)
> Reporter: Stefan Zoerner
> Priority: Critical
> Fix For: 1.0.1
>
> Attachments: FetchSchemaTest.java
>
>
> Trying to connect to ApacheDS with Softerra LDAP Administrator fails. The tool states that schema loading failed, and refuses to browse the directory at all afterwards.
> Other tools are able to read the schema and connect, for instance JXplorer.
> In order to investigate the problem further, I found out that some JNDI operations, which try to fetch the schema, have problems as well. I'll attach a suitable JUnit test for that soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.