Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Medium
Fix Version/s: 3.13
Affects Version/s: 3.11
Component/s: Infrastructure & Services - Application Lifecycle
Labels:
- affects-server
- concurrency

Introduced in Version:
3.11

Since JiraCachingPropertySet is not threadsafe, lazy initialisation and unsafe use of it needs concurrency controls.

See NPE stack traces in attached log file

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

weirdshit.txt
30/Oct/2007 2:02 AM
669 kB
Chris Mountford

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

Assignee:: Jed Wesley-Smith (Inactive)
Reporter:: Chris Mountford
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: 30/Oct/2007 2:02 AM
Updated:: 27/Mar/2019 11:52 PM
Resolved:: 15/Jan/2008 6:10 AM