Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.11
-
3.11
-
Description
Since JiraCachingPropertySet is not threadsafe, lazy initialisation and unsafe use of it needs concurrency controls.
See NPE stack traces in attached log file
Attachments
Issue Links
- causes
-
JRASERVER-16058 Aggressive locking in JiraCachingPropertySet causes high contention
- Closed
- is duplicated by
-
JRASERVER-13778 java.lang.NullPointerException at com.atlassian.jira.propertyset.JiraCachingPropertySet.exists(JiraCachingPropertySet.java:386)
- Closed
- is related to
-
JRASERVER-13778 java.lang.NullPointerException at com.atlassian.jira.propertyset.JiraCachingPropertySet.exists(JiraCachingPropertySet.java:386)
- Closed