Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16069

"Named query not known: atluser.externalEntity_hasMembership" when using LDAP for users with AD integration

XMLWordPrintable

      Summary

      When an user with AD account logs in into Bamboo, the application logs are polluted with Hibernate related exceptions, related to a Hibernate query called atluser.externalEntity_hasMembership which cannot be found.

      Steps to Reproduce

      • Create a remote application link in Bamboo with an external application.
      • Log into Bamboo with an external user (AD integration).
      Expected Results
      • Application logs are clear and no exceptions are raised.
      Actual Results
      • Application logs are polluted with the following exception. In this case, Bamboo is figuring out if the application switcher icon (AKA hamburguer icon) is to be displayed, by checking if the external user has certain memberships.

      The below exception is thrown in the atlassian-bamboo.log file:

      2015-06-24 09:01:40,855 ERROR [http-bio-8443-exec-10] [DefaultUserAccessor] org.springframework.orm.hibernate3.HibernateSystemException: Named query not known: atluser.externalEntity_hasMembership; nested exception is org.hibernate.MappingException: Named query not known: atluser.externalEntity_hasMembership
com.atlassian.user.impl.RepositoryException: org.springframework.orm.hibernate3.HibernateSystemException: Named query not known: atluser.externalEntity_hasMembership; nested exception is org.hibernate.MappingException: Named query not known: atluser.externalEntity_hasMembership
	at com.atlassian.user.impl.hibernate3.HibernateGroupManager.hasExternalMembership(HibernateGroupManager.java:399)
	at com.atlassian.user.impl.hibernate3.HibernateGroupManager.hasMembership(HibernateGroupManager.java:357)
	at com.atlassian.user.impl.cache.CachingGroupManager.hasMembership(CachingGroupManager.java:170)
	at com.atlassian.user.impl.delegation.DelegatingGroupManager.hasMembership(DelegatingGroupManager.java:256)
	at sun.reflect.GeneratedMethodAccessor1117.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.atlassian.crowd.integration.atlassianuser.DynamicDelegationAccessor$DelegatingInvocationHandler.invoke(DynamicDelegationAccessor.java:125)
	at com.sun.proxy.$Proxy32.hasMembership(Unknown Source)
	at bucket.user.DefaultUserAccessor.hasMembership(DefaultUserAccessor.java:487)
	at bucket.user.DefaultUserAccessor.hasMembership(DefaultUserAccessor.java:511)
	at sun.reflect.GeneratedMethodAccessor948.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:98)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:2

      Workaround

      There's no workaround for this issue, a new version of Bamboo will be released.

            [BAM-16069] "Named query not known: atluser.externalEntity_hasMembership" when using LDAP for users with AD integration

            There are no comments yet on this issue.

              easenjo sthr (Inactive)
              rsperafico Rafael Sperafico (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: