Bug 305869 - An internal error occurred during: "Update Installed JREs".
Summary: An internal error occurred during: "Update Installed JREs".
Status: VERIFIED DUPLICATE of bug 305043
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.6 M7   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 11:42 EDT by Mike Wilson CLA
Modified: 2010-04-26 08:20 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Wilson CLA 2010-03-15 11:42:12 EDT
- started with an empty workspace
- imported a plug-in from the filesystem
- waited a few seconds
- the walkback shown below appeared

(Weird. It looks like this is running on the VM that came with OpenOffice. I also have the IBM Java 5 VM installed, which is what I expected to be running on.)

eclipse.buildId=I20100312-1448
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

Error
Mon Mar 15 11:28:45 EDT 2010
An internal error occurred during: "Update Installed JREs".

java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/org.eclipse.e4.webide,P/.org.eclipse.jdt.core.external.folders]
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:136)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:326)
at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:63)
at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:285)
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:117)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1914)
at org.eclipse.core.internal.resources.Project.touch(Project.java:1191)
at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:118)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:793)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:4833)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize(JREContainerInitializer.java:69)
at org.eclipse.jdt.internal.launching.LaunchingPlugin$VMChanges.rebind(LaunchingPlugin.java:298)
at org.eclipse.jdt.internal.launching.LaunchingPlugin$VMChanges.access$0(LaunchingPlugin.java:263)
at org.eclipse.jdt.internal.launching.LaunchingPlugin$1.run(LaunchingPlugin.java:251)
at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4768)
at org.eclipse.jdt.internal.launching.LaunchingPlugin$VMChanges.doit(LaunchingPlugin.java:255)
at org.eclipse.jdt.internal.launching.LaunchingPlugin$JREUpdateJob.run(LaunchingPlugin.java:335)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Darin Wright CLA 2010-03-15 13:23:30 EDT
Moving to JCore for comment. The debugger is setting the JRE classpath container using a job - but that job itself does not have any scheduling rule.
Comment 2 Olivier Thomann CLA 2010-03-15 13:28:47 EDT
Jay, please investigate.
Comment 3 Jay Arthanareeswaran CLA 2010-03-18 07:17:49 EDT
It is same as bug 305043.

*** This bug has been marked as a duplicate of bug 305043 ***
Comment 4 Ayushman Jain CLA 2010-04-26 08:01:16 EDT
Verified for 3.6M7 using build I20100424-2000.
Comment 5 Jay Arthanareeswaran CLA 2010-04-26 08:20:25 EDT
Verified.