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

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 5.9.3
Affects Version/s: 5.8.1
Component/s: User Management, Crowd & LDAP integration
Labels:
- support

Bug Fix Policy:
View Atlassian Server bug fix policy

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.

was cloned as

BAM-16135 "Named query not known: atluser.externalEntity_hasMembership" when using LDAP with SSO filter

Closed

is related to: BSP-19505 You do not have permission to view this issue

mentioned in: Page Failed to load; Page Failed to load

Form Name

Monique Khairuliana (Inactive) made changes - 19/Aug/2019 1:59 AM

Workflow	Original: Bamboo Workflow 2016 v1 - Restricted [ 1437221 ]	New: JAC Bug Workflow v3 [ 3381002 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 07/Jul/2016 3:48 AM

Workflow

Original: Bamboo Workflow 2016 v1 [ 1421895 ]

New: Bamboo Workflow 2016 v1 - Restricted [ 1437221 ]

Marek Went (Inactive) made changes - 16/Jun/2016 10:22 AM

Workflow

Original: Bamboo Workflow 2014 v2 [ 902892 ]

New: Bamboo Workflow 2016 v1 [ 1421895 ]

Michalina made changes - 07/Jan/2016 7:32 AM

Remote Link

New: This issue links to "Page (Extranet)" [ 148987 ]

sthr (Inactive) made changes - 13/Jul/2015 7:14 AM

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

sthr (Inactive) made changes - 13/Jul/2015 7:14 AM

Fix Version/s

New: 5.9.3 [ 55197 ]

sthr (Inactive) made changes - 13/Jul/2015 4:05 AM

Remote Link

New: This issue links to "Page (Extranet)" [ 110307 ]

sthr (Inactive) made changes - 13/Jul/2015 3:33 AM

Description

Original: h4. 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.

h4. 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:
{code}
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
{code}

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

New: h4. 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.

h4. Steps to Reproduce
- Create a remote application link in Bamboo with an external application.
- Log into Bamboo with an external user (AD integration).

h5. Expected Results
- Application logs are clear and no exceptions are raised.

h5. 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:
{code}
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
{code}

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

sthr (Inactive) made changes - 13/Jul/2015 3:32 AM

Description

Original: h4. 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.

h4. 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:
{code}
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
{code}

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

New: h4. 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.

h4. 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:
{code}
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
{code}

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

sthr (Inactive) made changes - 13/Jul/2015 3:31 AM

Description

Original: h4. 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
Step 1
Step 2
Expected Results
Actual Results
The below exception is thrown in the xxxxxxx.log file:
...
Notes
(Optional - If Necessary)
Workaround
(If there is no workaround directly say so)

{code}
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
{code}

New: h4. 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.

h4. 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:
{code}
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
{code}

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

Assignee:: sthr (Inactive)

Reporter:: Rafael Sperafico (Inactive)

Affected customers:: 0 This affects my team

Watchers:: 4 Start watching this issue

Created:: 24/Jun/2015 4:02 PM

Updated:: 19/Aug/2019 1:59 AM

Resolved:: 13/Jul/2015 7:14 AM

Details

Description

Summary

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Issue Links

Forms

Activity

People

Dates