Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » BundleStatusException when running with -consoleLog argument
BundleStatusException when running with -consoleLog argument [message #137216] Tue, 21 October 2008 09:01 Go to next message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
Dear all,
I am using (and extending) TPTP plug-in to do some static code analysis on
a project. Actually, everything seems fine and the bugs are correctly
reported after the analysis process is finished. But when I run the
analysis with the -consoleLog argument I see quite a list of exceptions
starting from:
" org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144) ".

Please note that the exception originates from eclipse code, not from my
plug-in extensions.

Could you please tell me what could be wrong? Are there any chances that
some bugs are not reported because of this exception?
(eclipse version: 3.4.0, TPTP version: 4.5.0)

Regards,
Yazdanshenas
Re: BundleStatusException when running with -consoleLog argument [message #137227 is a reply to message #137216] Tue, 21 October 2008 13:48 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Amir,

Could you please report the full exception here? It's hard to tell by just
the 2 line of exception here.

Eugene

"Amir Yazdanshenas" <amir4042@yahoo.com> wrote in message
news:9410faf2e5699ae008a9f21f49ae18b6$1@www.eclipse.org...
> Dear all,
> I am using (and extending) TPTP plug-in to do some static code analysis on
> a project. Actually, everything seems fine and the bugs are correctly
> reported after the analysis process is finished. But when I run the
> analysis with the -consoleLog argument I see quite a list of exceptions
> starting from:
> " org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144) ".
>
> Please note that the exception originates from eclipse code, not from my
> plug-in extensions.
>
> Could you please tell me what could be wrong? Are there any chances that
> some bugs are not reported because of this exception?
> (eclipse version: 3.4.0, TPTP version: 4.5.0)
>
> Regards,
> Yazdanshenas
>
>
>
Re: BundleStatusException when running with -consoleLog argument [message #137238 is a reply to message #137227] Tue, 21 October 2008 14:53 Go to previous messageGo to next message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
I hope you don't mind the lengthy message. The full console log is:


eclipse.buildId=I20080617-2000
java.version=1.6.0-rc
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.sdk.ide
Command-line arguments: -product org.eclipse.sdk.ide -data
D:\Academic\workspace/../Pasargad CRM Workspace -dev
file:D:/Academic/workspace/.metadata/.plugins/org.eclipse.pd e.core/Pasargad
CRM Workspace/dev.properties -os win32 -ws win32 -arch x86 -consoleLog

!ENTRY org.eclipse.jdt.core 4 4 2008-10-21 13:03:51.277
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.OutOfMemoryError: Java heap space
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.<init >(HashtableOfObject.java:38)
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.reh ash(HashtableOfObject.java:139)
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.put (HashtableOfObject.java:112)
at
org.eclipse.jdt.internal.core.index.DiskIndex.copyQueryResul ts(DiskIndex.java:349)
at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(Disk Index.java:522)
at org.eclipse.jdt.internal.core.index.Index.save(Index.java:18 1)
at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.s aveIndex(IndexManager.java:617)
at
org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIn dex.execute(AddJarFileToIndex.java:205)
at
org.eclipse.jdt.internal.core.search.processing.JobManager.r un(JobManager.java:394)
at java.lang.Thread.run(Unknown Source)
Exception in thread "Java indexing" java.lang.OutOfMemoryError: Java heap
space
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.<init >(HashtableOfObject.java:38)
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.reh ash(HashtableOfObject.java:139)
at
org.eclipse.jdt.internal.compiler.util.HashtableOfObject.put (HashtableOfObject.java:112)
at
org.eclipse.jdt.internal.core.index.DiskIndex.copyQueryResul ts(DiskIndex.java:349)
at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(Disk Index.java:522)
at org.eclipse.jdt.internal.core.index.Index.save(Index.java:18 1)
at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.s aveIndex(IndexManager.java:617)
at
org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIn dex.execute(AddJarFileToIndex.java:205)
at
org.eclipse.jdt.internal.core.search.processing.JobManager.r un(JobManager.java:394)
at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.osgi 2 0 2008-10-21 13:58:20.865
!MESSAGE While loading class
"org.eclipse.hyades.trace.ui.internal.core.TraceUIImages", thread
"Thread[main,6,main]" timed out waiting (5000ms) for thread
"Thread[Worker-9,5,main]" to finish starting bundle
" reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar
[374]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but
"org.eclipse.hyades.trace.ui.internal.core.TraceUIImages" may not be fully
initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle
" reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar "
by thread "Worker-9".
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by:
org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
... 39 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)


Regards,
Yazdanshenas
Re: BundleStatusException when running with -consoleLog argument [message #137250 is a reply to message #137227] Tue, 21 October 2008 15:04 Go to previous messageGo to next message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
Sorry for the wrong console log. This is the correct log:

eclipse.buildId=I20080617-2000
java.version=1.6.0-rc
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.sdk.ide
Command-line arguments: -product org.eclipse.sdk.ide -data
D:\Academic\workspace/../Bimeh Runtime Workspace -dev
file:D:/Academic/workspace/.metadata/.plugins/org.eclipse.pd e.core/Bimeh
Rutime Workspace/dev.properties -os win32 -ws win32 -arch x86 -consoleLog

!ENTRY org.eclipse.osgi 2 0 2008-10-21 18:32:52.608
!MESSAGE While loading class
"org.eclipse.hyades.trace.ui.internal.core.TraceUIImages", thread
"Thread[main,6,main]" timed out waiting (5000ms) for thread
"Thread[Worker-3,5,main]" to finish starting bundle
" reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar
[840]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but
"org.eclipse.hyades.trace.ui.internal.core.TraceUIImages" may not be fully
initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle
" reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar "
by thread "Worker-3".
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by:
org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
... 39 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

Regards
Yazdanshenas
Re: BundleStatusException when running with -consoleLog argument [message #137263 is a reply to message #137250] Tue, 21 October 2008 21:51 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Amir,

It looks like there is a bug in
org.eclipse.hyades.trace.ui.UIPlugin.start(BundleContext) where the Runnable
is having some threading issue. You mentioned that you are extending TPTP,
could you try running in debug mode and investigate further? I suspect the
Display.getDefault().asyncExec(runnable); may create potential problem.
Could you please open a bug with your log and steps to reproduce the
problem?

Eugene

"Amir Yazdanshenas" <amir4042@yahoo.com> wrote in message
news:1363d5df3231b2947d1e938f0ccb7112$1@www.eclipse.org...
> Sorry for the wrong console log. This is the correct log:
>
> eclipse.buildId=I20080617-2000
> java.version=1.6.0-rc
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.sdk.ide
> Command-line arguments: -product org.eclipse.sdk.ide -data
> D:\Academic\workspace/../Bimeh Runtime Workspace -dev
> file:D:/Academic/workspace/.metadata/.plugins/org.eclipse.pd e.core/Bimeh
> Rutime Workspace/dev.properties -os win32 -ws win32 -arch x86 -consoleLog
>
> !ENTRY org.eclipse.osgi 2 0 2008-10-21 18:32:52.608
> !MESSAGE While loading class
> "org.eclipse.hyades.trace.ui.internal.core.TraceUIImages", thread
> "Thread[main,6,main]" timed out waiting (5000ms) for thread
> "Thread[Worker-3,5,main]" to finish starting bundle
> " reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar
> [840]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but
> "org.eclipse.hyades.trace.ui.internal.core.TraceUIImages" may not be fully
> initialized.
> !STACK 0
> org.osgi.framework.BundleException: State change in progress for bundle
> " reference:file:/D:/Academic/eclipse/dropins/tptp.sdk-TPTP-4. 5.0/eclipse/plugins/org.eclipse.hyades.trace.ui_4.4.101.v200 806130100.jar "
> by thread "Worker-3".
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
> at
> org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> 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.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
> Caused by:
> org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
> ... 39 more
> Root exception:
> org.eclipse.osgi.framework.internal.core.AbstractBundle$Bund leStatusException
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.begi nStateChange(AbstractBundle.java:1144)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:263)
> at
> org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111)
> at
> org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl assInternal(BundleLoader.java:444)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:397)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:385)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa dClass(DefaultClassLoader.java:87)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> at java.lang.ClassLoader.loadClassInternal(Unknown Source)
> at org.eclipse.hyades.trace.ui.UIPlugin$1.run(UIPlugin.java:404 )
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:133)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3800)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :3425)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:21 98)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault (Realm.java:288)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start (IDEApplication.java:113)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:193)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:382)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> 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.equinox.launcher.Main.invokeFramework(Main.java: 549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>
> Regards
> Yazdanshenas
>
Re: BundleStatusException when running with -consoleLog argument [message #137275 is a reply to message #137263] Wed, 22 October 2008 06:45 Go to previous messageGo to next message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
Hi Eugene
I use two groups of analysis rules, one group from TPTP's owned rules, and
another group with my own analysis rules (extending from
AbstractAnalysisRule).

So I started to run each individual rule separately to find out which rule
is making the exception, and I found something strange: The rules are not
causing the problem.

The moment I click on the analysis drop-down menu in the second eclipse
workspace(the one that contains the plug-in extensions in runtime), the
console log of the first eclipse workspace (the one containing the source
code of the extensions) shows those exceptions. And again, when I close
the second workspace the console log of the first workspace shows those
exceptions.

So, it sounds like a mistake in the basic plug-in development
infrastructure, not a problem in TPTP, so I can't actually see what
happens in debug mode.

I guess you can reproduce the exception by:

1- create an plug-in development project with TPTP (I guess you already
know a lot more than I do, but I used this tutorial for that:
http://www.eclipse.org/tptp/home/documents/process/developme nt/static_analysis/TPTP_static_analysis_tutorial_part2.html)

2- Run the plug-in with the -consoleLog argument. (the second eclipse
appears on the screen)

3- Hit the analysis drop-down menu in the second eclipse workspace.

4- Check the console window in the first eclipse environment.

I just don't know what negative affects this might impose on the analysis
phase. Is it possible that some analysis errors escape?

Regards
Yazdanshenas
Re: BundleStatusException when running with -consoleLog argument [message #137283 is a reply to message #137275] Wed, 22 October 2008 15:49 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Amir,

According to the stack trace, it should have nothing to do with the analysis
code. It's simply the loading of some icon files of actions in toolbar, that
may be loaded when you clicked on the drop down menu. And it sounds like it
only happen when you have multiple instance of workbench running at the same
time, could you confirm that? I suspect the problem does not exist if you
run only one instance of Eclipse workbench.

I can take a further look at the problem. I will have to try reproduce the
problem first.

Eugene


"Amir Yazdanshenas" <amir4042@yahoo.com> wrote in message
news:19de558d67cc067df301016f5946d218$1@www.eclipse.org...
> Hi Eugene
> I use two groups of analysis rules, one group from TPTP's owned rules, and
> another group with my own analysis rules (extending from
> AbstractAnalysisRule).
>
> So I started to run each individual rule separately to find out which rule
> is making the exception, and I found something strange: The rules are not
> causing the problem.
>
> The moment I click on the analysis drop-down menu in the second eclipse
> workspace(the one that contains the plug-in extensions in runtime), the
> console log of the first eclipse workspace (the one containing the source
> code of the extensions) shows those exceptions. And again, when I close
> the second workspace the console log of the first workspace shows those
> exceptions.
>
> So, it sounds like a mistake in the basic plug-in development
> infrastructure, not a problem in TPTP, so I can't actually see what
> happens in debug mode.
> I guess you can reproduce the exception by:
>
> 1- create an plug-in development project with TPTP (I guess you already
> know a lot more than I do, but I used this tutorial for that:
> http://www.eclipse.org/tptp/home/documents/process/developme nt/static_analysis/TPTP_static_analysis_tutorial_part2.html)
>
> 2- Run the plug-in with the -consoleLog argument. (the second eclipse
> appears on the screen)
> 3- Hit the analysis drop-down menu in the second eclipse workspace.
>
> 4- Check the console window in the first eclipse environment.
>
> I just don't know what negative affects this might impose on the analysis
> phase. Is it possible that some analysis errors escape?
>
> Regards
> Yazdanshenas
>
Re: BundleStatusException when running with -consoleLog argument [message #137327 is a reply to message #137283] Thu, 23 October 2008 07:55 Go to previous messageGo to next message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
Hi Eugene,
I think I didn't fully understand what you mean by having one workbench
running.
When I am developing an eclipse plug-in, I am coding it in the host
workbench, and running/debugging it in another workbench. If I close the
host workbench, the second workbench automatically terminates, too. So I
have to have the two workbenches running.
Am I wrong?

Regards
Yazdanshenas
Re: BundleStatusException when running with -consoleLog argument [message #137479 is a reply to message #137327] Fri, 24 October 2008 14:07 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Amir,

You are right, that is the common way to develope on Eclipse platform.
Unless the problem is blocking your development, I think you can ignore the
exception for now. It should not generate any error in the code analysis as
it is something with a TPTP image loader class only.
If you could log a bugzilla defect with your stacktrace, that would help to
trace the problem as well.

Eugene


"Amir Yazdanshenas" <amir4042@yahoo.com> wrote in message
news:3eb3c162b90567651aa6635597dbc1ad$1@www.eclipse.org...
> Hi Eugene,
> I think I didn't fully understand what you mean by having one workbench
> running. When I am developing an eclipse plug-in, I am coding it in the
> host workbench, and running/debugging it in another workbench. If I close
> the host workbench, the second workbench automatically terminates, too. So
> I have to have the two workbenches running.
> Am I wrong?
>
> Regards
> Yazdanshenas
>
>
>
Re: BundleStatusException when running with -consoleLog argument [message #137525 is a reply to message #137479] Sun, 26 October 2008 05:40 Go to previous message
Amir Yazdanshenas is currently offline Amir Yazdanshenas
Messages: 8
Registered: July 2009
Junior Member
Hi Eugene,
Thanks for your time. Yes, I think I can ignore the problem for now. I'll
look into Bugzilla to post the problem.

Regards
Yazdanshenas
Previous Topic:EclipseCon 2009: Call for Participation
Next Topic:How to run AGR-Tests in standard-mode
Goto Forum:
  


Current Time: Sun Oct 26 07:18:04 GMT 2014

Powered by FUDForum. Page generated in 0.05159 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software