Community
Participate
Working Groups
prefix test name 181080 reference abstract output more explicit message when exit workbench and no space duplicate state open priority severity 3 target age 14 due product hasApar compName wsa.web.oti answer release symptom rm envName Win2000 phaseFound cvt level phaseInject addDate 2001/07/26 23:36:25 assignDate 2001/07/27 11:09:43 lastUpdate 2001/07/27 13:50:30 responseDate endDate ownerLogin decandio originLogin endres ownerName George DeCandio originName Kathy Endres ownerArea 9ZVA originArea AVALON apar pmr test tracks: none. verify: none. history: addDate action userLogin (userName) -------------------- --------------- ---------------------------------- 2001/07/26 23:36:25 open endres (Kathy Endres) 2001/07/27 07:02:49 note nabe (Watanabe, Takeshi) 2001/07/27 08:07:15 note wakao (Wakao, Masaki) 2001/07/27 11:09:43 assign asahata (Asahata, Tetsuro) 2001/07/27 13:48:06 note endres (Kathy Endres) 2001/07/27 13:48:28 modify endres (Kathy Endres) 2001/07/27 13:50:30 modify endres (Kathy Endres) duplicate defects: none. duplicate features: none. sizing: none. notes: <Note by endres (Kathy Endres), 2001/07/26 23:36:25, seq: 1 rel: 0 action: open> In testing on the 20010724-0100 R09 Packaged JDK build, I double-clicked on the system icon in the upperleft corner of the Workbench. This caused a Saving Problems dialog to appear with the following text: "Unable to store workbench state." HERE'S THE STEPS I DID AT THE TIME (NOTE: I can't confirm if this is reproducible since my workbench appears to still be messed up even after restarting it): 1. I had a JSP file open (I don't know if I opened it or if it was open upon restarting the Workbench ... I think the latter case applied, though) 1. created the Your Company web example 2. opened the index.html file that is directly under webApplication NOTE: the Design page was the open page when I did this NOTE: this is a frame file. I wanted to try it with a non-frame file, but as I noted, my workbench is messed up at this point 3. make a change to the file 4. double-click on the system icon in the upper left of the Workbench Saving Problems dialog appears as noted. NOTE: The standard out showed that 4 problems occurred in saving the workbench. 5. select OK on Saving Problems dialog 6. Save Resources prompt appears 7. select the No button The Workbench disappears, but a Problems saving workspace dialog appears with the following text: "Problems occurred while trying to save the state of the workbench." 8. select Details See "Could not write metadata for /." 9. select OK 10. restart the Workbench 11. Error dialog appears with the following text: "Unable to read workbench state. workbench.xml will be deleted." 12. select OK Workbench appears, but only J2EE perspective appears (lost any perspectives had previously opened) 13. opened the Web Perspective to verify projects and files were still there! 14. repeated step 4 and Saving problems dialog appeared again as before! After this, I used the Web Example and Web Project wizards and neither of them would close after selecting the Finish button and I noticed both projects did not contain an ibm-web-ext.xmi file under WEB-INF (should they or does this file get generated later?). I then tried the HTML File wizard and it closed after selecting Finish. Since I assume this is related to having a frame file open when I closed the workbench, I opened this defect against wsa.web.pageediting. If this problem is not related to PageEditing, please reroute this defect to the appropriate component. <Note by nabe (Watanabe, Takeshi), 2001/07/27 07:02:49, seq: 2 rel: 0 action: note> Asahata-san, It seems that a config file of workbench is broken. We cannot see that data from Yamato, so please contact Kathy-san, and take a look at the problem. Thank you. <Note by wakao (Wakao, Masaki), 2001/07/27 08:07:15, seq: 3 rel: 0 action: note> We think this is a Eclipse Workbench problem. Maybe the following file has been corrupted. workspace/.metadata/.plugins/org.eclipse.ui/workbench.xml Endres-san, Could you try to rename the file to another name and do the same scenario. If the problem is gone, this defect should be rerouted to was.prereq.workbench component. <Note by asahata (Asahata, Tetsuro), 2001/07/27 11:09:43, seq: 4 rel: 0 action: assign> George, Could you open OTI PR? Old Owner: asahata New Owner: decandio Old Component: wsa.web.pageediting New Component: wsa.web.oti <Note by endres (Kathy Endres), 2001/07/27 13:48:06, seq: 5 rel: 0 action: note> George said he suspected the problem was that I was out of space. I looked and the drive I installed the build on had a free space of 0. So, I'm bumping the severity of this from a 1 to 3. I recommend this be opened as an OTI defect to output a more explicit message. <Note by endres (Kathy Endres), 2001/07/27 13:48:28, seq: 6 rel: 0 action: modify> Old Severity: 1 New Severity: 3 <Note by endres (Kathy Endres), 2001/07/27 13:50:30, seq: 7 rel: 0 action: modify> Old Abstract: unable to store workbench state on Workbench exit New Abstract: output more explicit message when exit workbench and no space NOTES:
PRODUCT VERSION: R09, Win2000
Messages like this come from the Core component. DJ, Pls include this to your "Improved Servicability" work.
*** Bug 2370 has been marked as a duplicate of this bug. ***
I believe this is a problem with the JFace ErrorDialog. In this case we return a ResourceException that contains a status object: status message: Could not write metadata for /. status exception: IOException IOException message: (varies by VM, but this is the most explicit message you'll ever get. On IBM JRE it says something like, "Could not write <filename>. Not enough space on disk". The problem is, the JFace ErrorDialog only shows the status messages in the details area, not the status' exception's message. If it showed both we would get a clearer message in most cases. I suggest making this fix in ErrorDialog.populateList(...). Note that it should check for both null exceptions and null exception messages, some exceptions don't have a message. I will change "Could not write metadata for /." to "Could not write metadata for workspace".
In general we don't want to be showing internal exceptions and internal file names to the user. These are implementation details.
*** Bug 5939 has been marked as a duplicate of this bug. ***
If we don't want to show these than there is no other information we have. Should we close this PR?
Nick's comments are correct it is not appropriate to show internal exceptions to the user. The typical approach is to have the application catch these internal exceptions and present them in a form that is meaningful to the user. The best case occurs when the execption that the UI catches has enough information to determine the cause. Otherwise additional code needs to run to determine what really happened.
So are you suggesting that we do a check for this case and send a different message?
Checking against an error message does nto work for NL reasons. We should give a non specific but helpful message for this case and let the internal error be handled in the details.
*** Bug 19534 has been marked as a duplicate of this bug. ***
I just wasted about an hour of my time to figure out that I'd filled up my home directory. More explicit error messages would be nice. This bug has been open since 2001 and has had at least 3 duplicates closed. Anybody going to bother to fix this problem? It would be appreciated.
There are currently no plans to work on this feature
New Gerrit change created: https://git.eclipse.org/r/118356
Gerrit change https://git.eclipse.org/r/118356 was merged to [master]. Commit: http://git.eclipse.org/c/www.eclipse.org/eclipse.org-common.git/commit/?id=d4ed4b53b9819e785a1d4c2606a05bd2a1bdfac1
