Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363963

Summary: Provide ability to adjust default projector timeout value
Product: [Eclipse Project] Equinox Reporter: DJ Houghton <dj.houghton>
Component: p2Assignee: DJ Houghton <dj.houghton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: john.arthorne, krzysztof.daniel, leberre, pascal
Version: 3.6.2   
Target Milestone: 3.6.2+   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:
Bug Depends on: 336967    
Bug Blocks: 336968, 363964    
Attachments:
Description Flags
Patch for 368963 and 363965
none
Replacement 3.6.2 jar with fix
none
Replacement 3.6.2 jar with fix none

Description DJ Houghton CLA 2011-11-16 14:24:47 EST
Cloned to track release into 3.6.x stream.

+++ This bug was initially created as a clone of Bug #336967 +++

There have been a couple reports where we have huge systems with several thousand IUs and people are adding several IUs (same ids but multiple versions) via the reconciler and the solution that we get back from SAT4J isn't always the optimal one. As described in Bug 301446 comment 5 this is expected and the solutions are *not* incorrect. 

We should provide a mechanism to adjust the default timeout value so clients are able to use this in their problem investigations. I recommend a System property (key: eclipse.p2.projector.timeout) which would default to 1000 (current value) if the property doesn't exist or the property value can't be parsed.
Comment 1 DJ Houghton CLA 2011-11-16 16:47:10 EST
Created attachment 207118 [details]
Patch for 368963 and 363965

Here is a patch which allows the user to set the default conflict timeout value. It also includes a patch to Bug 363965 for simplified code to fix an unstable plan resolution.
Comment 3 John Arthorne CLA 2012-02-23 09:38:31 EST
Created attachment 211493 [details]
Replacement 3.6.2 jar with fix
Comment 4 John Arthorne CLA 2012-02-23 09:41:40 EST
Created attachment 211494 [details]
Replacement 3.6.2 jar with fix

Previous attachment had wrong bug#