"Failed to properly handle event com.atlassian.crowd.event.user.UserAttributeStoredEvent.." when connects to JIRA from external API

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

Symptoms

Everytime when the user tried to connect to JIRA using any external API application (such Eclipse IDE Connector), the followingappears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 9 10 11 12 13 2013-01-14 15:25:46.487787500 2013-01-14 15:25:46,486 TP-Processor2 WARN anonymous 925x5640x1 - 211.24.247.39,131.103.26.113 /rpc/soap/jirasoapservice-v2 [plugins.dvcs.listener.DvcsAddUserListener] Failed to properly handle event com.atlassian.crowd.event.user.UserAttributeStoredEvent@50c81872 for user sysadmin 2013-01-14 15:25:46.487790500 org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed 2013-01-14 15:25:46.487791500 at org.springframework.osgi.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:105) 2013-01-14 15:25:46.487799500 at org.springframework.osgi.service.importer.support.internal.support.RetryTemplate.execute(RetryTemplate.java:83) 2013-01-14 15:25:46.487800500 at org.springframework.osgi.service.importer.support.internal.aop.ServiceDynamicInterceptor.lookupService(ServiceDynamicInterceptor.java:430) 2013-01-14 15:25:46.487801500 at org.springframework.osgi.service.importer.support.internal.aop.ServiceDynamicInterceptor.getTarget(ServiceDynamicInterceptor.java:415) . . . . . .

Cause

This most likely caused by JIRA DVCS connector plugins where it was trying to connect to Crowd database to listen to user attributes.

Resolution

  1. Shutdown your JIRA server.

  2. Remove the plugins cache from the following directories:

    (JIRA_HOME)/plugins/.bundled-plugins

    (JIRA_HOME)/plugins/.osgi-plugins

  3. Startup JIRA server again.

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.