[#JRA-13461] Scheduler can cause deadlock during Data Import

JIRA

Scheduler can cause deadlock during Data Import

Created: 03/Sep/07 01:05 AM Updated: 12/Feb/08 02:49 AM

Component/s:

Import / Export, Services

Affects Version/s:

None

Fix Version/s:

3.13.x

Time Tracking:

Not Specified

File Attachments:

runaway_service.txt (58 kB)
2.

stack.txt (79 kB)

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-10541~~ Scheduler/PicoContainer deadlock.

Participants:	Anton Mazkovoi [Atlassian], Brenden Bain [Atlassian], Jed Wesley-Smith [Atlassian] and Nick Menere [Atlassian]
Since last comment:	34 weeks, 5 days ago
Labels:

Description

« Hide

Discovered that the scheduler can cause deadlocks with DataImport.

This is a result of 2 things:

We call - schedUtil.shutdownScheduler(sched);
This in turn calls - scheduler.shutdown(); This does not block until services are finished.
We should call - scheduler.shutdown(true); (and have a timeout on the operation too).
Webworks inherited thread local problem. Anton knows the details of this.

The attached thread dump contains the deadlock.
Note that there are three threads with the name - JiraQuartzScheduler_Worker-0

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brenden Bain [Atlassian] added a comment - 02/Dec/07 09:51 PM

Another example stack trace that was returned during internal testing.

[ Permlink | « Hide ]

Jed Wesley-Smith [Atlassian] added a comment - 06/Dec/07 08:00 PM

The fix for this issue has not been able to make it into JIRA v3.12. We are hoping to incorporate it into v3.12.1. As of writing however, there are 163 items scheduled as Fix For v3.12.1. We will not be able to include all of them.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 12/Feb/08 02:49 AM

Another thread dump can be found on ~~JRA-10541~~.