-
Bug
-
Resolution: Fixed
-
Low
-
7.13.6, 7.6.15, 8.5.1
-
7.06
-
1
-
Severity 2 - Major
-
8
-
Issue Summary
- Project copy based on existing configurations performs very slow or fails when there are custom fields configured per project context.
Steps to Reproduce
- Prepare 30-40 custom fields and configure them for selected project.
- Create number of issues for this project (10-20)
- Provide constant background load (20 - 30 users) that retrieves random issues (via REST service /issue/{key})
- Run concurrent project create operation based on existing configuration (with per context fields) on behalf of ~7 users
Expected Results
New projects are crated successfully , there are no timeouts/errors for background issue read operations
Actual Results
Threads locked on getContexts operation should be observed within thread dump
sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304) com.atlassian.util.concurrent.LazyReference$Sync.get(LazyReference.java:244) com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:147) com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112) com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:92) com.atlassian.jira.issue.fields.config.FieldConfigSchemeImpl.getContexts(FieldConfigSchemeImpl.java:94)
Workaround
Run create project operation during maintenance break with administrator's exclusive access.
- relates to
-
-
- Gathering Impact
-
-
JRASERVER-68168 Make FieldLayoutCache population more efficient in Jira
- Gathering Interest
-
PSR-347 Loading...
- mentioned in
-
-
-
-
-
-
-
-