| WTP 0.7 Final - internal error at startup: "initializing Java tooling" [message #139822] |
Tue, 20 September 2005 20:53  |
Eclipse User |
|
|
|
Originally posted by: laurentd75___no.sp_am.yahoo.fr
Hi,
A strange error has just happened to me when starting up Eclipse (this
particular install is the WTP 0.7 "all-in-one" final release for Win32 on XP
with an additional third-party plugin: the Jigloo 3.5.2 GUI builder)
Right after startup, just after the dialogue window indicating workspace
refresh in progress closed, an alert window popped up with the following
message:
An internal error has occured: "Initializing Java tooling"
I clicked OK to dismiss it, and didn't experience any further problems
though, I could run both a Web project and a Swing project that are in this
worspace.
Has anyone experienced this alert ?
Here's what gets dumped in my workspace's metadata/.log file. I can't really
tell whether it's related to Eclipse or WTP:
!SESSION 2005-09-20
22:41:00.31 ------------------------------------------------
eclipse.buildId=I20050627-1435
java.version=1.4.2_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog
!ENTRY org.eclipse.core.runtime 4 2 2005-09-20 22:41:20.218
!MESSAGE An internal error occurred during: "Initializing Java tooling".
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: -1
at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.jav a:846)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.remove(Bas
icNotifierImpl.java:143)
at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.jav a:794)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.remove(Bas
icNotifierImpl.java:137)
at
org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterI mpl.removeAdapte
rs(EMF2DOMAdapterImpl.java:670)
at
org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterI mpl.removeAdapte
rs(EMF2DOMAdapterImpl.java:677)
at
org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterI mpl.removeAdapte
rs(EMF2DOMAdapterImpl.java:677)
at org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterI mpl.removeAd
apters(EMF2DOMAdapterImpl.java:677)
at
org.eclipse.wst.common.internal.emf.resource.EMF2DOMAdapterI mpl.removeAdapte
rs(EMF2DOMAdapterImpl.java:677)
at
org.eclipse.wst.common.internal.emf.resource.EMF2DOMRenderer .preUnload(EMF2D
OMRenderer.java:245)
at
org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.doUnload
(TranslatorResourceImpl.java:185)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.unload(Reso urceImpl.java:11
01)
at
org.eclipse.wst.common.internal.emf.resource.ReferencedXMIRe sourceImpl.unloa
dIfNecessary(ReferencedXMIResourceImpl.java:135)
at
org.eclipse.wst.common.internal.emf.resource.ReferencedXMIRe sourceImpl.relea
seFromRead(ReferencedXMIResourceImpl.java:188)
at
org.eclipse.wst.common.internal.emf.resource.TranslatorResou rceImpl.releaseF
romRead(TranslatorResourceImpl.java:343)
at
org.eclipse.wst.common.componentcore.internal.ModuleStructur alModel.release(
ModuleStructuralModel.java:64)
at
org.eclipse.wst.common.internal.emfworkbench.integration.Edi tModel.release(E
ditModel.java:979)
at
org.eclipse.wst.common.internal.emfworkbench.integration.Edi tModel.releaseRe
sources(EditModel.java:1001)
at
org.eclipse.wst.common.internal.emfworkbench.integration.Edi tModel.releaseAc
cess(EditModel.java:959)
at
org.eclipse.wst.common.componentcore.internal.StructureEdit. dispose(Structur
eEdit.java:463)
at
org.eclipse.wst.common.componentcore.internal.resources.Virt ualContainer.mem
bers(VirtualContainer.java:192)
at
org.eclipse.wst.common.componentcore.internal.resources.Virt ualContainer.mem
bers(VirtualContainer.java:135)
at
org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjec tContainer. <init
>(FlexibleProjectContainer.java:136)
at
org.eclipse.jst.j2ee.internal.web.classpath.WebAppContainer. <init>(WebAppCon
tainer.java:48)
at
org.eclipse.jst.j2ee.internal.web.classpath.WebAppContainerI nitializer.initi
alize(WebAppContainerInitializer.java:34)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeCon tainer(JavaModel
Manager.java:1591)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathC ontainer(JavaMod
elManager.java:1040)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore .java:1326)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspa th(JavaProject.j
ava:2039)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspa th(JavaProject.j
ava:1947)
at
org.eclipse.jdt.internal.core.search.JavaSearchScope.add(Jav aSearchScope.jav
a:108)
at
org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.init ialize(JavaWorks
paceScope.java:84)
at
org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.
java:62)
at
org.eclipse.jdt.internal.core.search.JavaSearchScope.<init>(JavaSearchScope.
java:58)
at
org.eclipse.jdt.internal.core.search.JavaWorkspaceScope.<init >(JavaWorkspace
Scope.java:29)
at
org.eclipse.jdt.internal.core.JavaModelManager.getWorkspaceS cope(JavaModelMa
nager.java:1421)
at
org.eclipse.jdt.internal.core.search.BasicSearchEngine.creat eWorkspaceScope(
BasicSearchEngine.java:157)
at
org.eclipse.jdt.core.search.SearchEngine.createWorkspaceScop e(SearchEngine.j
ava:392)
at org.eclipse.jdt.core.JavaCore$1.run(JavaCore.java:2623)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
|
|
|
|
|
| Re: WTP 0.7 Final - internal error at startup: "initializing Java tooling" [message #140771 is a reply to message #140485] |
Tue, 27 September 2005 04:45  |
| Eclipse User |
|
|
|
Originally posted by: l.dokov.enless-soft.coom
Hi, Laurent, the same happened to me when I moved from Eclipse 3.0 to
Eclipse 3.1 "all-in-one", I thing the same version you described. I think it
was due to the workspace because it contained some settings that were in an
old format or something like that. It only happened once and after restart
of the Eclipse no further error messages. I guess it is nothing to be
worried about.
|
|
|
| Re: WTP 0.7 Final - internal error at startup: "initializing Java tooling" [message #140801 is a reply to message #140771] |
Tue, 27 September 2005 01:28 |
| Eclipse User |
|
|
|
Originally posted by: laurentd75___no.sp_am.yahoo.fr
"Liubomir Dokov" wrote:
> Hi, Laurent, the same happened to me when I moved from Eclipse 3.0 to
> Eclipse 3.1 "all-in-one", I thing the same version you described. I think
it
> was due to the workspace because it contained some settings that were in
an
> old format or something like that. It only happened once and after restart
> of the Eclipse no further error messages. I guess it is nothing to be
> worried about.
>
Hi again Lubomir, how is it going ? ;-)
Thanks for your suggestion but I'm 100% sure this was a new workspace
created specifically with WTP 0.7, so in my case this rules out the
hypothesis of an old workspace causing problems with the new version...
You're right though in that this doesn't seem a major problem, however I
suppose I'll file a bug report anyway so the WTP team can look into it and
fix whatever causes this behaviour..
Cheers,
Laurent
|
|
|
Powered by
FUDForum. Page generated in 0.03033 seconds
] 
Search
Help
Register
Login
Home
