[ https://issues.apache.org/jira/browse/OAK-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382124#comment-17382124 ]
Konrad Windszus edited comment on OAK-9497 at 7/16/21, 3:12 PM: ---------------------------------------------------------------- I could reproduce with the last commit on trunk. The full stack trace is {code} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.jackrabbit.oak.security.authentication.ldap.LdapServerClassLoader$Proxy.lambda$1(LdapServerClassLoader.java:157) at java.lang.Thread.run(Thread.java:748) Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.; remaining name 'cn=foobargroup,dc=example,dc=com' at com.sun.jndi.ldap.Connection.readReply(Connection.java:479) at com.sun.jndi.ldap.LdapClient.processReply(LdapClient.java:881) at com.sun.jndi.ldap.LdapClient.modify(LdapClient.java:955) at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1404) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:257) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:167) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:156) at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:157) at org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.addMembers(InternalLdapServer.java:93) ... 6 more {code} with {{Proxy.addMembers}} being called from {{LargeLdapProviderTest.beforeClass}} Sometimes I get this slightly different exception {code} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.jackrabbit.oak.security.authentication.ldap.LdapServerClassLoader$Proxy.lambda$1(LdapServerClassLoader.java:157) at java.lang.Thread.run(Thread.java:748) Caused by: javax.naming.NamingException: LDAP connection has been closed; remaining name 'cn=foobargroup,dc=example,dc=com' at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133) at com.sun.jndi.ldap.Connection.readReply(Connection.java:469) at com.sun.jndi.ldap.LdapClient.processReply(LdapClient.java:887) at com.sun.jndi.ldap.LdapClient.modify(LdapClient.java:961) at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1432) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:257) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:167) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:156) at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:157) at org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.addMembers(InternalLdapServer.java:93) ... 6 more {code} was (Author: kwin): I could reproduce with the last commit on trunk. The full stack trace is {code} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.jackrabbit.oak.security.authentication.ldap.LdapServerClassLoader$Proxy.lambda$1(LdapServerClassLoader.java:157) at java.lang.Thread.run(Thread.java:748) Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.; remaining name 'cn=foobargroup,dc=example,dc=com' at com.sun.jndi.ldap.Connection.readReply(Connection.java:479) at com.sun.jndi.ldap.LdapClient.processReply(LdapClient.java:881) at com.sun.jndi.ldap.LdapClient.modify(LdapClient.java:955) at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1404) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:257) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:167) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:156) at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:157) at org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.addMembers(InternalLdapServer.java:93) ... 6 more {code} with {{Proxy.addMembers}} being called from {{LargeLdapProviderTest.beforeClass}} > LargeLdapProviderTest: InvocationTargetException: LDAP connection has been > closed > --------------------------------------------------------------------------------- > > Key: OAK-9497 > URL: https://issues.apache.org/jira/browse/OAK-9497 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-ldap > Affects Versions: 1.22.8 > Reporter: Konrad Windszus > Priority: Major > > With Mac OS 11.4 I run into the following exception when executing the test > phase in Maven > {code} > [ERROR] > org.apache.jackrabbit.oak.security.authentication.ldap.LargeLdapProviderTest > Time elapsed: 1.939 s <<< ERROR! > java.lang.reflect.InvocationTargetException > Caused by: javax.naming.NamingException: LDAP connection has been closed > {code} > I can reproduce reliably on my computer > This happens with > {code} > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > Maven home: /usr/local/Cellar/maven/3.8.1/libexec > Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: > /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home > Default locale: en_DE, platform encoding: UTF-8 > OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac" > {code} > I tried with JDK 8 (1.8.0_292) as well with the same exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)