'javax.naming.PartialResultException Unprocessed Continuation Reference' when using LDAP due to LDAP Referrals
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Troubleshoot issues relating to LDAP referrals in Confluence 3.4.x and below.
Diagnosis
When using LDAP, an error like the following appears in the logs:
2007-01-18 16:29:20,857 ERROR [http-8080-Processor23] [bucket.user.DefaultUserAccessor]
getGroups com.atlassian.user.impl.RepositoryException: javax.naming.PartialResultException: Unprocessed Continuation Reference(s);Cause
In Confluence 3.4.x and below, the LDAP integration does not support referrals by default.
Solution
This error message can usually be safely ignored.
This has been fixed in Confluence 3.5 and later (CONF-9116). More information about LDAP referrals can be found from Java's site.
Workaround
To enable referrals, add the following JVM parameter to the startup script of your application server.
-Datlassian.java.naming.referral=followIf you experience any problems with the workaround, revert the change and ignore or hide the error message:
Edit
<confluence install>/confluence/WEB-INF/classes/log4j.propertiesAdd the line:
log4j.logger.com.atlassian.user.impl.delegation.DelegatingGroupManager=FATALWas this helpful?