Bug #43

Possible race in TaskInvoker$TaskConfig

Added by Ingo Lütkebohle over 12 years ago. Updated over 12 years ago.

Status:ClosedStart date:2012-07-19
Priority:HighDue date:
Assignee:Ingo Lütkebohle% Done:

100%

Category:appsEstimated time:2.00 hours
Target version:1.8

Description

It is not entirely clear, but there may be a race in TaskInvoker$TaskConfig.stateChanged when triggerEvent itself causes invocations on the same task-config instance, but in a different thread.

Associated revisions

Revision 2357
Added by Ingo Lütkebohle over 12 years ago

Convert TaskInvoker to use ReentrantLock around critical sections only, instead of judicious use of synchronized on whole methods. refs #43

History

#1 Updated by Ingo Lütkebohle over 12 years ago

  • Description updated (diff)
  • Status changed from New to In Progress

#2 Updated by Ingo Lütkebohle over 12 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
  • Estimated time set to 2.00

The problem was probably in XTT itself, because of a race between placing newly created tasks into the internal book-keeping data-structure, and getting network events for them. Fixed in r2383

Also available in: Atom PDF