Bug 1079944 - [QE] (6.2.x) org.jboss.as.test.integration.naming.ldap.LdapUrlInSearchBaseTestCase fails on IBMJDK 1.6 due to 'Invalid root Dn given'
Summary: [QE] (6.2.x) org.jboss.as.test.integration.naming.ldap.LdapUrlInSearchBaseTes...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security, Testsuite
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Josef Cacek
QA Contact: Josef Cacek
Russell Dickenson
URL:
Whiteboard:
Depends On: 1078246
Blocks: 1099440
TreeView+ depends on / blocked
 
Reported: 2014-03-24 11:12 UTC by Pavel Jelinek
Modified: 2014-07-25 10:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 1078246
Environment:
IBMJDK 1.6
Last Closed: 2014-07-25 10:59:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBQA-9997 0 Major Open org.jboss.as.test.integration.naming.ldap.LdapUrlInSearchBaseTestCase fails on IBMJDK 1.6 due to 'Invalid root Dn given' 2014-07-30 09:40:34 UTC

Description Pavel Jelinek 2014-03-24 11:12:38 UTC
Occures in EAP 6.2.2 as well 
See:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP-6.2.x-CP/view/EAP-6.2.x-CP-jobs/job/eap-62x-patched-as-testsuite-RHEL-matrix-IBMJDK6/24/jdk=ibm16,label_exp=RHEL6%26%26x86_64/testReport/org.jboss.as.test.integration.naming.ldap/LdapUrlInSearchBaseTestCase/

+++ This bug was initially created as a clone of Bug #1078246 +++

Standard Output

[0m08:40:02,872 INFO  [org.jboss.as.test.integration.security.common.Utils] (main) Requesting URL http://10.16.180.63:8080/ldap-test/?host=10.16.180.63
08:40:03,374 ERROR [org.apache.directory.shared.ldap.codec.actions.searchRequest.StoreSearchRequestBaseObject] (NioProcessor-5) Invalid root Dn given : ldap: (0x6C 0x64 0x61 0x70 0x3A ) is invalid : ERR_04202 A value is missing on some RDN
[31m08:40:03,461 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/ldap-test].[org.jboss.as.test.integration.naming.ldap.LdapUrlTestServlet]] (http-/10.16.180.63:8080-3) JBWEB000236: Servlet.service() for servlet org.jboss.as.test.integration.naming.ldap.LdapUrlTestServlet threw exception: javax.naming.InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given : ldap: (0x6C 0x64 0x61 0x70 0x3A ) is invalid]; Remaining name: 'ldap://10.16.180.63:10389/dc=jboss,dc=org'
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3017) [rt.jar:1.6.0]
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2832) [rt.jar:1.6.0]
	at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1026) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.ComponentContext.c_resolveIntermediate_nns(ComponentContext.java:164) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.AtomicContext.c_resolveIntermediate_nns(AtomicContext.java:354) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.ComponentContext.p_resolveIntermediate(ComponentContext.java:435) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:372) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:350) [rt.jar:1.6.0]
	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:333) [rt.jar:1.6.0]
	at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:250) [jndi.jar:]
	at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:250) [jndi.jar:]
	at org.jboss.as.test.integration.naming.ldap.LdapUrlTestServlet.runSearch(LdapUrlTestServlet.java:111) [classes:]
	at org.jboss.as.test.integration.naming.ldap.LdapUrlTestServlet.doGet(LdapUrlTestServlet.java:73) [classes:]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-4.jar:7.4.0.Final-redhat-4]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:340) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.0.Beta4.jar:7.4.0.Beta4]
	at java.lang.Thread.run(Thread.java:761) [vm.jar:1.6.0]

[0m

See: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL-matrix-IBMJDK6/jdk=ibm16,label_exp=RHEL6%26%26x86_64/70/testReport/org.jboss.as.test.integration.naming.ldap/LdapUrlInSearchBaseTestCase/testDir/

Comment 1 Pavel Jelinek 2014-07-25 10:59:20 UTC
This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Enterprise Application Platform please feel free to open a bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.