Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-38038

JiraCachingPropertySet.init race condition with ApplicationPropertiesImpl.asMap

      There are two plugins involved:

      Zephyr related stacktrace(1 thread, probably zombie - still processed by Tomcat, but timeout by apache proxy):

      	at com.atlassian.jira.propertyset.PropertySetCache.cloneProperty(PropertySetCache.java:350)
      	at com.atlassian.jira.propertyset.PropertySetCache.bulkLoad(PropertySetCache.java:315)
      	at com.atlassian.jira.propertyset.JiraCachingPropertySet.init(JiraCachingPropertySet.java:789)
      	at com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:58)
      	at com.opensymphony.module.propertyset.PropertySetManager.getInstance(PropertySetManager.java:31)
      	at com.thed.zephyr.util.JiraUtil.getPropertySet(JiraUtil.java:131)
      	at com.thed.zephyr.je.conditions.IsIssueTypeTestCondition.shouldDisplay(IsIssueTypeTestCondition.java:18)
      	at com.atlassian.jira.plugin.webfragment.conditions.AbstractIssueCondition.shouldDisplay(AbstractIssueCondition.java:37)
      	at com.atlassian.jira.plugin.webfragment.conditions.AbstractJiraCondition.shouldDisplay(AbstractJiraCondition.java:40)
      	at com.atlassian.plugin.web.DefaultWebInterfaceManager.filterFragmentsByCondition(DefaultWebInterfaceManager.java:172)

      Stateoscope related threads(many, waiting for lock):

      	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
      	at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214)
      	at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290)
      	at com.atlassian.jira.propertyset.JiraCachingPropertySet.getType(JiraCachingPropertySet.java:651)
      	at com.atlassian.jira.propertyset.JiraCachingPropertySet.getAsActualType(JiraCachingPropertySet.java:88)
      	at com.atlassian.jira.config.properties.ApplicationPropertiesStore.getPropertiesAsMap(ApplicationPropertiesStore.java:304)
      	at com.atlassian.jira.config.properties.ApplicationPropertiesImpl.asMap(ApplicationPropertiesImpl.java:103)
      	at com.tuncaysenturk.jira.plugins.S.getActions(StateoscopeTabPanel.java:123)
      	at com.tuncaysenturk.jira.plugins.S.showPanel(StateoscopeTabPanel.java:216)
      	at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanel3Adaptor.showPanel(IssueTabPanel3Adaptor.java:36)
      	at com.atlassian.jira.plugin.issuetabpanel.IssueTabPanelInvokerImpl.invokeShowPanel(IssueTabPanelInvokerImpl.java:43)

            [JRASERVER-38038] JiraCachingPropertySet.init race condition with ApplicationPropertiesImpl.asMap

            Atlassian Update – 20 June 2021

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Daria Misiowiec
            Jira Bugmaster

            Daria Misiowiec added a comment - Atlassian Update – 20 June 2021 Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Daria Misiowiec Jira Bugmaster

              Unassigned Unassigned
              pcora Pedro Cora
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: