| RC3 loading problem [message #255560] |
Fri, 25 June 2004 07:00  |
Eclipse User |
|
|
|
Since RC3 is out, I'm constantly receiving the following message right after
workbench loading, and also experiencing 5 second delay, which is very
annoying as slows down the plugin development process.
While loading class
" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine ",
thread "main" timed out waiting (5000ms) for thread "Worker-0" to finish
starting bundle "org.eclipse.team.cvs.ui". To avoid deadlock, thread "main"
is proceeding but
" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine " may
not be fully initialized.
I tried to find an answer in the news/bugzilla but did not succeed. Any
idea?
Thanx
/Leo
|
|
|
|
| Re: RC3 loading problem [message #256041 is a reply to message #255586] |
Sun, 27 June 2004 09:50  |
| Eclipse User |
|
|
|
I've just intstalled 3.0 release (build 200406251208) from scratch. But the
problem still exists.
While loading class
" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine ",
thread "main" timed out waiting (5000ms) for thread "Worker-0" to finish
starting bundle "org.eclipse.team.cvs.ui". To avoid deadlock, thread "main"
is proceeding but
" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine " may
not be fully initialized.
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLoca lClass(EclipseCl
assLoader.java:102)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleL
oader.java:371)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader
..java:402)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader. loadClass(Abstra
ctClassLoader.java:93)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at
org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument.ge tLines(ConsoleDo
cument.java:78)
at
org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.d ump(CVSOutputCon
sole.java:150)
at
org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.a ccess$1(CVSOutpu
tConsole.java:147)
at
org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole$1 .run(CVSOutputCo
nsole.java:118)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:106)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2749)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2434)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
java:335)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
at org.eclipse.core.launcher.Main.run(Main.java:644)
at org.eclipse.core.launcher.Main.main(Main.java:628)
----- Original Message -----
From: "Pascal Rapicault" <pascal@ibm.canada>
Newsgroups: eclipse.platform
Sent: Friday, June 25, 2004 2:01 PM
Subject: Re: RC3 loading problem
> I believe this has been fixed in later builds.
>
> PaScaL
>
> Leonid Mokrushin wrote:
>
> > Since RC3 is out, I'm constantly receiving the following message right
after
> > workbench loading, and also experiencing 5 second delay, which is very
> > annoying as slows down the plugin development process.
> >
> > While loading class
> > " org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine ",
> > thread "main" timed out waiting (5000ms) for thread "Worker-0" to finish
> > starting bundle "org.eclipse.team.cvs.ui". To avoid deadlock, thread
"main"
> > is proceeding but
> > " org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine "
may
> > not be fully initialized.
> >
> > I tried to find an answer in the news/bugzilla but did not succeed. Any
> > idea?
> >
> > Thanx
> > /Leo
> >
> >
|
|
|
| Re: RC3 loading problem [message #256094 is a reply to message #256041] |
Sun, 27 June 2004 11:12 |
| Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
The CVS team looked at the problem and guaranteed the fact that this is
not a problem.
PaScaL
Leonid Mokrushin wrote:
> I've just intstalled 3.0 release (build 200406251208) from scratch. But the
> problem still exists.
>
> While loading class
> " org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine ",
> thread "main" timed out waiting (5000ms) for thread "Worker-0" to finish
> starting bundle "org.eclipse.team.cvs.ui". To avoid deadlock, thread "main"
> is proceeding but
> " org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine " may
> not be fully initialized.
>
> java.lang.Exception: Generated exception.
> at
> org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLoca lClass(EclipseCl
> assLoader.java:102)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleL
> oader.java:371)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader
> .java:402)
> at
> org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader. loadClass(Abstra
> ctClassLoader.java:93)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at
> org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument.ge tLines(ConsoleDo
> cument.java:78)
> at
> org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.d ump(CVSOutputCon
> sole.java:150)
> at
> org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole.a ccess$1(CVSOutpu
> tConsole.java:147)
> at
> org.eclipse.team.internal.ccvs.ui.console.CVSOutputConsole$1 .run(CVSOutputCo
> nsole.java:118)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:106)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2749)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2434)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.
> java:335)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
> at org.eclipse.core.launcher.Main.run(Main.java:644)
> at org.eclipse.core.launcher.Main.main(Main.java:628)
>
> ----- Original Message -----
> From: "Pascal Rapicault" <pascal@ibm.canada>
> Newsgroups: eclipse.platform
> Sent: Friday, June 25, 2004 2:01 PM
> Subject: Re: RC3 loading problem
>
>
>
>>I believe this has been fixed in later builds.
>>
>>PaScaL
>>
>>Leonid Mokrushin wrote:
>>
>>
>>>Since RC3 is out, I'm constantly receiving the following message right
>
> after
>
>>>workbench loading, and also experiencing 5 second delay, which is very
>>>annoying as slows down the plugin development process.
>>>
>>>While loading class
>>>" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine ",
>>>thread "main" timed out waiting (5000ms) for thread "Worker-0" to finish
>>>starting bundle "org.eclipse.team.cvs.ui". To avoid deadlock, thread
>
> "main"
>
>>>is proceeding but
>>>" org.eclipse.team.internal.ccvs.ui.console.ConsoleDocument$Co nsoleLine "
>
> may
>
>>>not be fully initialized.
>>>
>>>I tried to find an answer in the news/bugzilla but did not succeed. Any
>>>idea?
>>>
>>>Thanx
>>>/Leo
>>>
>>>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.08612 seconds
Home