Bug 55511 - [Workbench] misleading error message when unable to set the value of the instance
Summary: [Workbench] misleading error message when unable to set the value of the inst...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
: 56150 58303 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-03-22 09:10 EST by Jeff McAffer CLA
Modified: 2021-09-20 15:47 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2004-03-22 09:10:39 EST 
In the event that the UI plugin is unable to set the value of the instance 
location messages such as
   "Error occurred in runtime.  Workspace cannot be set.  Exiting."
are being logged and/or displayed to the user in a dialog.

This is causing the Core team to get numerous bug reports when in fact there is 
nothing wrong with the runtime.  The workspace location was simply already 
set.  Everything is performing as expected.
Comment 1 Rafael Chaves CLA 2004-03-24 12:49:49 EST 
Also, an IOException and a lock that didn't succeed because another instance got
the lock first will give the same feedback to the user. 

Previously (M7), when another instance got the lock first, we used to get the
following message from the launcher:

"Another session is already running in the associated workspace. If this is not
the case, please delete the \".lock\" file in the workspace \".metadata\"
directory and try starting the platform again."
Comment 2 Rafael Chaves CLA 2004-03-24 14:02:18 EST 
Ok, I just saw the right message being shown when an workspace is picked using
the UI. The wrong message I mentioned above seems to be only presented when
starting with -data.
Comment 3 Jeff McAffer CLA 2004-03-25 11:27:58 EST 
*** Bug 56150 has been marked as a duplicate of this bug. ***
Comment 4 Rafael Chaves CLA 2004-04-13 18:29:29 EDT 
*** Bug 58303 has been marked as a duplicate of this bug. ***
Comment 5 Tod Creasey CLA 2007-06-14 08:38:22 EDT 
There are currently no plans to work on this although we would be happy to review patches.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:18:30 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 7 Eclipse Genie CLA 2021-09-20 15:47:22 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.