The startup time of the Jira node is significantly prolonged due to Group Ambassadors plugin.
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
This article describes a scenario in which the initialization process of a Jira node takes a significant amount of time due to Group Ambassadors plugin.
Environment
8.20.x
Diagnosis
According to the atlassian-jira.log, it appears that the startup process of Jira took longer than anticipated.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 172023-06-26 11:08:49,216+0200 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] **************** Jira starting... **************** 2023-06-26 11:08:49,296+0200 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] -------------- 2023-06-26 11:44:41,205+0200 localhost-startStop-1 INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve. 2023-06-26 11:44:41,210+0200 localhost-startStop-1 INFO [c.a.jira.startup.LauncherContextListener] Memory Usage: --------------------------------------------------------------------------------- Heap memory : Used: 11662 MiB. Committed: 31744 MiB. Max: 31744 MiB Non-heap memory : Used: 985 MiB. Committed: 1035 MiB. Max: 1536 MiB --------------------------------------------------------------------------------- TOTAL : Used: 12647 MiB. Committed: 32779 MiB. Max: 33280 MiB ---------------------------------------------------------------------------------The examination of the thread dump has disclosed that the implementation of demanding user operations in the database is being performed by Group Ambassadors plugin.
1 2 3 4com.atlassian.jira.security.groups.RequestCachingGroupManager.getAllGroups(RequestCachingGroupManager.java:68) com.caritteprod.group.ambassadors.util.GAUserListener.onStart(GAUserListener.java:130) com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$1.accept(DefaultLifecycleManager.java:265) com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$1.accept(DefaultLifecycleManager.java:262)
Solution
The issue appears to be related to version 2.4.2 of the Group Ambassadors plugin.
The issue has been resolved by upgrading the version to 2.4.5, which can be found at Group Ambassadors plugin.
Was this helpful?