Ticket #69 (closed enhancement: fixed)

Opened 12 months ago

Last modified 7 months ago

OTEquinox should use the new equinox adaptor hook

Reported by: stephan Owned by: stephan
Priority: major Milestone: OTDT_1.2.0
Component: otequinox Version: 1.1.6
Keywords: Cc:

Description

In Eclipse bug 208591 new adaptor-hooks for equinox are proposed. These hooks help solving a locking issue which we currently avoid by calling non-public methods (via reflection) in order to participate in the global locking.

Once these hooks are released and once we migrate to that eclipse version we should switch our implementation to using these new hooks.

Change History

Changed 12 months ago by stephan

  • status changed from new to assigned

Patches r17921 and r17922 in branches/experimental/new_adaptor_hooks indeed use the new hooks. In an OTDT 1.1.x this can be deployed manually along with a patched org.eclipse.osgi.

If no deadlocks occur with this version the branch will be merged back into trunk once we migrate to Eclipse 3.4 (given that the hooks are released to 3.4), thus the target OTDT_1.2.0.

Changed 7 months ago by stephan

  • status changed from assigned to closed
  • resolution set to fixed

Above patches have been used as the root for migration to Eclispe 3.4. As such the new adaptor hooks are indeed used and behave well. However, the original deadlock still occurs (see #122)!

Still the new adaptor hooks are a great help because now we don't have to change that part of the implementation when switching to a different synchronization strategy. The framework takes care of all synchronization and only calls us in an appropriate context.

Note: See TracTickets for help on using tickets.