Anonymizing users process takes long time to complete
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Anonymizing users process takes long time (around 30-40 minutes) to complete for single user.
Environment
Jira 8.7 and above.
Diagnosis
Following logs are logged in
atlassian-jira.log
when user anonymization is slow:atlassian-jira.log2022-02-07 18:20:21,484+0100 http-nio-8080-exec-3 ERROR admin 1066x19217x1 6jig1d 192.168.0.109,127.0.0.1 /rest/api/2/user/anonymization [c.m.j.p.e.gdpr.anonymizers.AuditLogEntryAnonymizer] java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy5989.getEmailBody(Unknown Source) at com.metainf.jira.plugin.emailissue.gdpr.anonymizers.AuditLogEntryAnonymizer.getAffectedEntity_Anonymization(AuditLogEntryAnonymizer.java:92) at com.metainf.jira.plugin.emailissue.gdpr.anonymizers.AuditLogEntryAnonymizer.getAffectedEntity_Anonymization(AuditLogEntryAnonymizer.java:12) at com.metainf.jira.plugin.emailissue.gdpr.anonymizers.AbstractAnonymizer.getAffectedEntities(AbstractAnonymizer.java:82) at com.metainf.jira.plugin.emailissue.gdpr.AnonymizationHandler.getAffectedEntitiesProcess(AnonymizationHandler.java:25) at com.metainf.jira.plugin.emailissue.gdpr.UserAnonymizationHandlerImpl.getAffectedEntities(UserAnonymizationHandlerImpl.java:50) at com.metainf.jira.plugin.emailissue.gdpr.UserAnonymizationHandlerImpl.getAffectedEntities(UserAnonymizationHandlerImpl.java:16) at com.atlassian.jira.user.anonymize.UserPropertyChangeManager.lambda$getAffectedEntitiesFromHandler$2(UserPropertyChangeManager.java:147) at com.atlassian.jira.user.anonymize.UserPropertyChangeManager.retryOnException(UserPropertyChangeManager.java:211) at com.atlassian.jira.user.anonymize.UserPropertyChangeManager.getAffectedEntitiesFromHandler(UserPropertyChangeManager.java:147) at com.atlassian.jira.user.anonymize.UserPropertyChangeManager.getAffectedEntities(UserPropertyChangeManager.java:72)
2022-02-08 15:34:12,582+0100 http-nio-8080-exec-46 INFO admin 934x21639x1 16hr5sw 192.168.0.109,127.0.0.1 /rest/api/2/user/anonymization [c.a.j.user.anonymize.DefaultAnonymizeUserService] User key is already anonymized (JIRAUSER123456), no need to change it 2022-02-08 15:34:12,584+0100 http-nio-8080-exec-46 INFO admin 934x21639x1 16hr5sw 192.168.0.109,127.0.0.1 /rest/api/2/user/anonymization [c.a.j.user.anonymize.DefaultAnonymizeUserService] Username is not anonymized (abc@mytestdomain.com), should rename to (jirauser123456) ... ... ... 2022-02-08 16:05:11,383+0100 JiraTaskExecutionThread-3 INFO admin 935x21653x1 16hr5sw 192.168.0.109,127.0.0.1 /rest/api/2/user/anonymization [c.a.j.user.anonymize.UserPropertyChangeManager] Ending task (success) for handler:
Log shows stack trace stuck at
com.metainf.jira.plugin.emailissue.gdpr.anonymizers.AuditLogEntryAnonymizer.getAffectedEntity_Anonymization
which referring to Email This Issue.
Cause
The problem is caused by Email This Issue plugin.
Solution
- Disable Email This Issue
- Reach out to Plugin vendor to inform the vendor about the issue with Email This Issue plugin
Third-party apps are not supported by Atlassian mentioned in Atlassian Support Offerings. Users may reach out to the vendor of the plugin for further assistance.