Bug 141588 - [ErrorHandling] an error message describing the osgi.locking startup problem would be helpful
Summary: [ErrorHandling] an error message describing the osgi.locking startup problem ...
Status: RESOLVED DUPLICATE of bug 59780
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC HP-UX
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Kim Horne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-12 13:56 EDT by Grant Gayed CLA
Modified: 2007-10-29 11:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2006-05-12 13:56:52 EDT
3.2RC4

Background: For some reason our hpux box is unable to create a .lock file for new workspaces on NFS servers, so we work around this by specifying system property -Dosgi.locking=none at startup time.  This is a known workaround that has been used for ~ 2 years, and is not isolated to our hpux box (it has been reported on installations of other *ix flavours as well, though no one seems sure of the underlying cause).

During testing I accidentally tried to self-host on our hpux box without specifying the -Dosgi.locking=none property for the runtime workspace, and I got an error dialog with the very helpful message "...you probably need to define -Dosgi.locking=none...".  Unfortunately someone who gets this far probably already knows this because they had to use this to get their original workspace running in the first place.  It would be very helpful if a similar error message could be shown when first starting eclipse as well, not just when self-hosting.
Comment 1 Andrey Loskutov CLA 2007-10-22 16:52:03 EDT
Isn't this one a dup of bug 59780?
Comment 2 Grant Gayed CLA 2007-10-29 11:12:18 EDT
Thanks for pointing this out, marking report as a duplicate.


*** This bug has been marked as a duplicate of bug 59780 ***