Eclipse plugin: crash on saving document

[Baron Selling]

Since a week I'm using the Eclipse plug-in(Trial-Version), it's ismply fantastic! But since a few days it's causing more problems than smiles. It crashes very often. For example, "oXgen document validation" detects an "Message:F java.util.EmptyStackException" error, when I try to save the document Eclipse will hang and "hibernates" forever. After restarting there's the following error in Eclipse's "Error-log".

hile loading class "ro.sync.exml.D.I", thread "Worker-2" timed out waiting (5000ms) for thread "main" to finish starting bundle "com.oxygenxml.editor". To avoid deadlock, thread "Worker-2" is proceeding but "ro.sync.exml.D.I" may not be fully initialized.

Error 2006-02-13 15:27:21.773 While loading class "ro.sync.exml.D.I", thread "Worker-2" timed out waiting (5000ms) for thread "main" to finish starting bundle "com.oxygenxml.editor". To avoid deadlock, thread "Worker-2" is proceeding but "ro.sync.exml.D.I" may not be fully initialized.
java.lang.Exception: Generated exception.
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:108)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:337)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:389)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:350)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:78)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at ro.sync.exml.D.E.E(Unknown Source)
at ro.sync.exml.D.E.B(Unknown Source)
at com.oxygenxml.editor.license.B.B(Unknown Source)
at com.oxygenxml.editor.license.C$1.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

What's wrong?

[sorin_ristache]

Hello,

The error message in the Eclipse error log says the <oXygen/> plugin could not be initialized in 5000 miliseconds, that is 5 seconds, so Eclipse will continue loading without waiting for <oXygen/> initialization. That means the initialization of the <oXygen/> plugin does not lock Eclipse loading more than 5 seconds. <oXygen/> initialization continues in background, but the main Eclipse thread will not wait for it. That means you should be able to use the <oXygen/> plugin when Eclipse initialization is completed.

I think the crashes and hangs are not caused by the <oXygen/> plugin. We did not experience them on any test machine. Are there any other users experiencing them ? Anyway we need more data about your particular installation to understand what goes wrong. It will be helpful if you contact us by email at support at oxygenxml dot com to tell you how to enable logging in <oXygen/>, generate a log file and send it to us. The log file will show if they are <oXygen/> related problems.

Regards,
Sorin