Bug 114777

Summary: Starting eclipse instance before another exits corrupts workspace
Product: [Retired] Red Hat Developer Suite Reporter: Jeremy Handcock <handcock>
Component: PlatformAssignee: eclipse-bugs
Status: CLOSED CURRENTRELEASE QA Contact: eclipse-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: jpound
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-01 17:30:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
.log trace none

Description Jeremy Handcock 2004-02-02 19:30:55 UTC 
Description of problem:

The eclipse process takes a while to exit after I close the
application.  If I start another instance of eclipse before the first
one has completely exited, there are errors at startup and the
workspace settings appear to be corrupted.

Version-Release number of selected component (if applicable):
eclipse-2.1.1-4


How reproducible: Always


Steps to Reproduce:
1. Start up eclipse
2. Exit eclipse
3. Start up eclipse again, before the first instance has had a chance
to exit completely
  
Actual results:
Many error dialogs at startup, including the following output on the
console:

Unable to find element factory:
org.eclipse.ui.internal.model.ResourceFactory
Unable to restore pagee - cannot instantiate input factory:
org.eclipse.ui.internal.model.ResourceFactory
Could not create view: org.eclipse.ui.views.ResourceNavigator
Unable to find view label: org.eclipse.ui.views.BookmarkNavigator
Could not create view: org.eclipse.ui.views.ContentOutline
Could not create view: org.eclipse.ui.views.TaskList
Unable to find Action Set: org.eclipse.ui.NavigateActionSet

Workspace settings appear corrupted, views are not open.

Expected results: Eclipse startup should proceed as normal.

Additional info: Will attach .log trace.
Comment 1 Jeremy Handcock 2004-02-02 19:33:42 UTC 
Created attachment 97412 [details]
.log trace

This log shows problems in starting the application server (for the help) and
in creating the views that appear in a normal startup.
Comment 2 Jeff Pound 2004-12-01 17:30:20 UTC 
This seems to work fine with RHDS 2.0