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/08/02 09:48:13 UTC
[jira] Created: (DIRSERVER-693) Can't connect with JXplorer
Can't connect with JXplorer
---------------------------
Key: DIRSERVER-693
URL: http://issues.apache.org/jira/browse/DIRSERVER-693
Project: Directory ApacheDS
Issue Type: Bug
Components: core
Affects Versions: pre-1.0
Reporter: Jörg Henne
Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Updated: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Jörg Henne updated DIRSERVER-693:
---------------------------------
Attachment: fix-toString.patch
Use StringBuffer.append(Object) instead of StringBuffer.append(Object.toString()) to prevent NPEs.
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12428238 ]
Alex Karasulu commented on DIRSERVER-693:
-----------------------------------------
This still happening ?
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Assigned: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Emmanuel Lecharny reassigned DIRSERVER-693:
-------------------------------------------
Assignee: Alex Karasulu
One more for Alex !
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Updated: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Jörg Henne updated DIRSERVER-693:
---------------------------------
Attachment: connect-via-JXplorer.txt
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: connect-via-JXplorer.txt
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12428357 ]
Jörg Henne commented on DIRSERVER-693:
--------------------------------------
The problems I initially reported should be fixed by the various patches applied within the last days/weeks. However, I can't verify this, since with the current trunk I can't even start ds:
Exception in thread "Main Thread" javax.naming.NamingException: OID for name 'postalAddress' was not found within the OID registry
at org.apache.directory.server.core.schema.bootstrap.BootstrapOidRegistry.getOid(BootstrapOidRegistry.java:99)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.lookup(BootstrapAttributeTypeRegistry.java:160)
at org.apache.directory.server.core.schema.bootstrap.AbstractBootstrapProducer$BootstrapAttributeType.getSuperior(AbstractBootstrapProducer.java:245)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.registerDescendants(BootstrapAttributeTypeRegistry.java:127)[11:56:01] WARN [org.apache.directory.server.core.schema.OidRegistryMonitorAdapter] - Failed to resolve OID: postalAddress
javax.naming.NamingException: OID for name 'postalAddress' was not found within the OID registry
at org.apache.directory.server.core.schema.bootstrap.BootstrapOidRegistry.getOid(BootstrapOidRegistry.java:99)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.lookup(BootstrapAttributeTypeRegistry.java:160)
at org.apache.directory.server.core.schema.bootstrap.AbstractBootstrapProducer$BootstrapAttributeType.getSuperior(AbstractBootstrapProducer.java:245)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.registerDescendants(BootstrapAttributeTypeRegistry.java:127)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.register(BootstrapAttributeTypeRegistry.java:114)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.register(BootstrapSchemaLoader.java:268)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.access$000(BootstrapSchemaLoader.java:67)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader$1.schemaObjectProduced(BootstrapSchemaLoader.java:81)
at org.apache.directory.server.core.schema.bootstrap.CoreAttributeTypeProducer.produce(CoreAttributeTypeProducer.java:176)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.load(BootstrapSchemaLoader.java:210)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.loadDepsFirst(BootstrapSchemaLoader.java:187)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.loadDepsFirst(BootstrapSchemaLoader.java:183)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.load(BootstrapSchemaLoader.java:129)
at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:739)
at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:226)
at org.apache.directory.server.core.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:114)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
at org.apache.directory.server.Service.init(Service.java:93)
at org.apache.directory.server.UberjarMain.main(UberjarMain.java:51)
at org.apache.directory.server.core.schema.bootstrap.BootstrapAttributeTypeRegistry.register(BootstrapAttributeTypeRegistry.java:114)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.register(BootstrapSchemaLoader.java:268)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.access$000(BootstrapSchemaLoader.java:67)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader$1.schemaObjectProduced(BootstrapSchemaLoader.java:81)
at org.apache.directory.server.core.schema.bootstrap.CoreAttributeTypeProducer.produce(CoreAttributeTypeProducer.java:176)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.load(BootstrapSchemaLoader.java:210)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.loadDepsFirst(BootstrapSchemaLoader.java:187)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.loadDepsFirst(BootstrapSchemaLoader.java:183)
at org.apache.directory.server.core.schema.bootstrap.BootstrapSchemaLoader.load(BootstrapSchemaLoader.java:129)
at org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:739)
at org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:226)
at org.apache.directory.server.core.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:114)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
at org.apache.directory.server.Service.init(Service.java:93)
at org.apache.directory.server.UberjarMain.main(UberjarMain.java:51)
Additionally, "mvn -Dintegration -fn test" fails for several sub-projects.
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12425631 ]
Emmanuel Lecharny commented on DIRSERVER-693:
---------------------------------------------
I have fixed the toString problem (I don't let the default toString to print "(null)", I return an empty String instead)
The second pb is for Alex, I think :)
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Updated: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Jörg Henne updated DIRSERVER-693:
---------------------------------
Attachment: fix-for-jxplorer-problem.patch
Ok, so I found some time to look into this problem. It seems like the optimized version did no longer supply the "subschemasubentry" attribute to JXplorer when being asked for it. This was due to the DefaultPartitionNexus only returning results when being asked for "*", "1.1" or "+" but not when being asked for specific attributes.
The attached patch fixes the problem. However, I don't really understand the implications of it. Furthermore, it is likely to cause deoptimization ;-)
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12428371 ]
Jörg Henne commented on DIRSERVER-693:
--------------------------------------
*cough*
Sorry, my fault: mvn clean did the trick.
However, connecting using JXplorer still doesn't work, since the schema is not served. Please see the attached fix-for-jxplorer-problem.patch.
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Assigned: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Alex Karasulu reassigned DIRSERVER-693:
---------------------------------------
Assignee: Alex Karasulu (was: Alex Karasulu)
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Updated: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Jörg Henne updated DIRSERVER-693:
---------------------------------
Attachment: after-fix.log
After fixing LdapResult, not LdapDN as I erroneously said (please see patch, It'll make the code more robust as StringBuffer.append(Object) can deal with null-references), I get an exception similar to the one I reported yesterday (see attached log).
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Jörg Henne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12425264 ]
Jörg Henne commented on DIRSERVER-693:
--------------------------------------
Version #423997 introduced a new way to handle the special attributes "1.1", "*" and "+". With this change, the DefaultPartitionNexus stopped providing client-requested attributes, If neither of the above mentioned special attributes were requested.
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12428358 ]
Emmanuel Lecharny commented on DIRSERVER-693:
---------------------------------------------
Are you using trunks, or branches/apacheds/1.0-trunks?
In any case, do you do a mvn clean before doing a mvn install and a mvn -Dintegration test ?
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Commented: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Ersin Er (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=comments#action_12425239 ]
Ersin Er commented on DIRSERVER-693:
------------------------------------
We need to investigate the disappearance of subscemaSubentry attribute. Anyone knows why it happened? Was it intended?
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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
[jira] Closed: (DIRSERVER-693) Can't connect with JXplorer
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-693?page=all ]
Alex Karasulu closed DIRSERVER-693.
-----------------------------------
Fix Version/s: 1.1.0
1.0-RC4
Resolution: Fixed
Applied Jorg's patch to 1.0 in 431981 and to 1.1 in 431983.
> Can't connect with JXplorer
> ---------------------------
>
> Key: DIRSERVER-693
> URL: http://issues.apache.org/jira/browse/DIRSERVER-693
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: pre-1.0
> Reporter: Jörg Henne
> Assigned To: Alex Karasulu
> Fix For: 1.1.0, 1.0-RC4
>
> Attachments: after-fix.log, connect-via-JXplorer.txt, fix-for-jxplorer-problem.patch, fix-toString.patch
>
>
> Connecting with JXplorer leads to the NPE in LdapDN as I reported on the list earlier. Please see the complete log.
--
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