Oxygen XML Forum

Eclipse launch hangs with the following .metadata/.log (partial) content, on reboot, after a windows shutdown with eclipse & oxygenxml still running.

My work-around has been to delete the .metadata/ directory in the affected workspace, then reboot Eclipse, but I loose settings.

Is there a better workaround?

Should I report this as a bug?

I'm running Eclipse 3.3.1.1, XP and OxygenXml 8.2.0

Bill.

==================

!SESSION 2008-06-02 11:10:47.421 -----------------------------------------------
eclipse.buildId=M20071023-1652
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
Framework arguments: -showlocation
Command-line arguments: -os win32 -ws win32 -arch x86 -showlocation -clean

This is a continuation of log file C:\ewkshop\workspaces\01-epeer-group\bspaces-wksp\.metadata\.bak_6.log
Created Time: 2008-06-02 11:56:43.015

!ENTRY org.eclipse.osgi 2 0 2008-06-02 11:56:43.015
!MESSAGE While loading class "com.oxygenxml.editor.editors.A.A", thread "Thread[main,6,main]" timed out waiting (5000ms) for thread "Thread[Worker-0,5,main]" to finish starting bundle "update@../../../install-sites/wynn-installs/eclipse/plugins/com.oxygenxml.editor_8.2.0/ [154]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "com.oxygenxml.editor.editors.A.A" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "update@../../../install-sites/wynn-installs/eclipse/plugins/com.oxygenxml.editor_8.2.0/" by thread "Worker-0".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1141)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:258)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:408)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at com.oxygenxml.editor.editors.xml.h.Ä›(Unknown Source)
at com.oxygenxml.editor.editors.xml.h.createPages(Unknown Source)

..... truncated here

==================

Hi Bill,

The behavior you described could not be reproduced by us.
Please also note that the stack trace you sent us is not the reason for which the Eclipse hangs, it is just a warning that some of the oXygen classes were not loaded in a specific time slice.

Try to delete from the "configuration" directory of the Eclipse installation all its content except the config.ini file.

Best regards,
Mircea

Mircea,

Thanks for the much better workaround. My templates survived,
and the affected workspace is usable again.

Bill.

Mircea,

About that workaround being better. I spoke in haste. Deleteing everything
except config.ini in /eclipse/configuration also dropped my third party
installs, including OxygenXml. After re-installing them via the update
mgr, the system seems normal again.

Do you have any other suggestion for closing in on my problem?

Bill.

Hi Bill,

The new problem you encountered (regarding the third party plugins lost) leads me to the conclusion that there was actually something wrong with the Eclipse installation itself, since deleting some files from the '/eclipse/configuration' should not affect the installed plugins in any way.
My strong suggestion is to install a fresh new Eclipse... We use the 3.3.2 version in production and we never encountered such problems. Is there any particular reason for using 3.3.1.1 ?

More regards,
Mircea

Mircea,

Good idea for many reasons: its time to upgrade. Thanks,

Bill.

Hi!

I'm using eclipse 3.4 and oxygen eclipse plugin 9.3 on osx 10.5.4.

I see the following errormessage im my console.log:

03.07.08 14.14.37 [0x0-0x1d41d4].org.eclipse.eclipse[6578] !MESSAGE While loading class "ro.sync.exml.I.C.A", thread "Thread[main,6,main]" timed out waiting (5000ms) for thread "Thread[Worker-5,5,main]" to finish starting bundle "reference:file:plugins/com.oxygenxml.editor_9.3.0/ [600]". To avoid deadlock, thread "Thread[main,6,main]" is proceeding but "ro.sync.exml.I.C.A" may not be fully initialized.
03.07.08 14.14.37 [0x0-0x1d41d4].org.eclipse.eclipse[6578] !STACK 0
03.07.08 14.14.37 [0x0-0x1d41d4].org.eclipse.eclipse[6578] org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.oxygenxml.editor_9.3.0/" by thread "Worker-5".
03.07.08 14.14.37 [0x0-0x1d41d4].org.eclipse.eclipse[6578] at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
03.07.08 14.14.37 [0x0-0x1d41d4].org.eclipse.eclipse[6578] at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:263)


I posted in this thread since the stacktrace looked similar.


-Kaj

Hello,

Yes, the stacktrace is similar, it is generated when loading the Oxygen plugin and the reason is the same: some Oxygen classes were not loaded in a specific time slice. It is a warning caused by some long initializations that take more than 5 seconds which is the Eclipse time slice for initializing a plugin. From our tests it is only a warning and Oxygen always works correctly when Eclipse posts this stacktrace to the Eclipse log. If you see any problems when working with XML files in the Oxygen plugin please let us know.


Thank you,
Sorin