Eclipse constantly crashing - could not resolve mylyn module - eclipse

My installation of Eclipse 2022-09 is crashing constantly, either it freezes and then crashes, or just crashes silently.
I've noticed that it happens when the code completion tooltip is triggered, but not always.
On restart the error log contains the following
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.mylyn.team.ui [2581]
Unresolved requirement: Require-Bundle: org.eclipse.mylyn.tasks.ui; bundle-version="[3.8.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.mylyn.tasks.ui; bundle-version="3.25.2.v20200814-0512"; singleton:="true"
org.eclipse.mylyn.tasks.ui [2580]
Unresolved requirement: Require-Bundle: org.eclipse.mylyn.commons.notifications.feed; bundle-version="1.0.0"
-> Bundle-SymbolicName: org.eclipse.mylyn.commons.notifications.feed; bundle-version="1.17.2.v20200813-0821"; singleton:="true"
org.eclipse.mylyn.commons.notifications.feed [2553]
No resolution report for the bundle. Bundle was not resolved because of a uses constraint violation.
org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] and jakarta.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="jakarta.xml.bind"] via two dependency chains.
Chain 1:
org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"]
require: (&(osgi.wiring.bundle=javax.xml.bind)(bundle-version>=2.2.0))
|
provide: osgi.wiring.bundle: javax.xml.bind
javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"]
Chain 2:
org.eclipse.mylyn.commons.notifications.feed [osgi.identity; type="osgi.bundle"; version:Version="1.17.2.v20200813-0821"; osgi.identity="org.eclipse.mylyn.commons.notifications.feed"; singleton:="true"]
require: (&(osgi.wiring.bundle=com.sun.xml.bind)(bundle-version>=2.2.0))
|
provide: osgi.wiring.bundle; bundle-version:Version="2.3.3.v20201118-1818"; osgi.wiring.bundle="com.sun.xml.bind"
com.sun.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="com.sun.xml.bind"]
import: (&(osgi.wiring.package=javax.xml.bind)(&(version>=2.3.3)(!(version>=2.3.4))))
|
export: osgi.wiring.package: javax.xml.bind
jakarta.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.3.3.v20201118-1818"; osgi.identity="jakarta.xml.bind"]
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1786)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
Short of a reinstall, can this be fixed?
After removing Mylyn, as recommended, the crashes are still occuring, with the following in the error log view
Still crashing, pasting in code into a window is causing the crashes, albeit intermittently.
This is in the error log
eclipse.buildId=4.25.0.I20220831-1800
java.version=19
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_IE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
org.eclipse.core.resources
Warning
Fri Oct 14 15:48:23 IST 2022
The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

Related

Eclipse RCP build - Unresolved requirement: com.sun.jna

I just installed Eclipse 2022-06 (4.24.0) and built and export default RCP application product.
When I try to run this product in windows I get error in log file listed below. (in Eclipse IDE environment it runs perfectly).
It looks like library com.sun.jna is missing... But it included in required plug-ins.
It exists in config.ini and plugins folder of built product as well...
I spent two days trying to solve this issue and ran out of ides already...
!SESSION 2022-08-16 14:25:08.798 -----------------------------------------------
eclipse.buildId=unknown
java.version=18.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -clearPersistedState
Command-line arguments: -os win32 -ws win32 -arch x86_64 -clearPersistedState
!ENTRY org.eclipse.e4.ui.workbench.addons.swt 4 0 2022-08-16 14:25:09.361
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.e4.ui.workbench.addons.swt [42]
Unresolved requirement: Import-Package: org.eclipse.e4.ui.internal.workbench.swt
-> Export-Package: org.eclipse.e4.ui.internal.workbench.swt; bundle-symbolic-name="org.eclipse.e4.ui.workbench.swt"; bundle-version="0.16.500.v20220506-1520"; version="0.0.0"; x-friends:="org.eclipse.e4.ui.workbench.addons.swt,org.eclipse.e4.ui.workbench.renderers.swt,org.eclipse.ui.workbench"
org.eclipse.e4.ui.workbench.swt [44]
Unresolved requirement: Require-Bundle: org.eclipse.urischeme; bundle-version="1.1.0"
-> Bundle-SymbolicName: org.eclipse.urischeme; bundle-version="1.2.100.v20211001-1648"; singleton:="true"
org.eclipse.urischeme [64]
Unresolved requirement: Require-Bundle: com.sun.jna; bundle-version="[5.8.0,6.0.0)"
Unresolved requirement: Require-Bundle: org.eclipse.e4.ui.workbench.renderers.swt; bundle-version="0.9.1"
-> Bundle-SymbolicName: org.eclipse.e4.ui.workbench.renderers.swt; bundle-version="0.15.500.v20220511-1638"; singleton:="true"
org.eclipse.e4.ui.workbench.renderers.swt [43]
Unresolved requirement: Require-Bundle: org.eclipse.e4.ui.workbench.swt; bundle-version="0.9.0"
-> Bundle-SymbolicName: org.eclipse.e4.ui.workbench.swt; bundle-version="0.16.500.v20220506-1520"; singleton:="true"
at org.eclipse.osgi.container.Module.start(Module.java:463)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
As greg-449 suggests problem was with version of com.sun.jna...
Version 4.5.1 was included by default instead of 5.8.0.
So, to solve this, I added version requirements for com.sun.jna in *.product file "Contents" tab.

Startup delay due to OSGI bundle resolving

I'm currently trying to migrate our product to work on jdk 11 and as a part of this effort upgraded the osgi framework (upgrading from equinox osgi version 3.9.1.v20130814-1242). We managed to upgrade the components and start the pack but currently we see high startup time (startup freezes in the middle for some additional time). we suspect it is due to bundle wiring.
I checked the bundle status using ss comand and all the bundles were in Active state.
Then I enabled osgi debug logs for wiring (org.eclipse.osgi/resolver/wiring) and notice one component trying to wire to same component repeatedly
Following is a part of the log. similar repeated logs for different components can be seen during this startup freeze time . (I attached the full log in http://download2265.mediafire.com/cov16dra60kg/n808avzytuv3xxb/logs.txt)
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
RESOLVER: Wirings for resolved bundles:
Resource
osgi.identity; osgi.identity="tomcat"; type="osgi.bundle"; version:Version="7.0.85.wso2v1"
Wiring
[1] osgi.wiring.package; filter:="(osgi.wiring.package=*)"; resolution:="dynamic"; cardinality:="multiple" -> [osgi.identity; osgi.identity="axiom"; type="osgi.bundle"; version:Version="1.2.11.wso2v12"]
Can anyone please help me in identifying the problem and why it tries to wire to same package (any additional methods to narrowdown the issue). Same tomcat version was used in the old OSGI version but didn't see this kind of freezing in the middle.
Thanks a lot

BIRT RCP report designer 4.6.0 problems: could not resolve module: org.eclipse.birt.chart.examples

I have installed BIRT RCP designer 4.6.0 on a server machine 64 with:
w12r2, java 1.7, eclipse Kepler 1.
when i start birt.exe i obtained a crash with this log:
!SESSION 2017-06-22 11:39:45.295 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_80
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.birt.chart.examples 4 0 2017-06-22 11:39:46.576
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.birt.chart.examples [51]
Unresolved requirement: Require-Bundle: org.eclipse.ui.ide; bundle-version="[3.2.0,4.0.0)"; resolution:="optional"
Unresolved requirement: Require-Bundle: org.eclipse.ui.workbench.texteditor; bundle-version="[3.2.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.ui.workbench.texteditor; bundle-version="3.10.0.v20160530-2011"; singleton:="true"
org.eclipse.ui.workbench.texteditor [269]
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Unresolved requirement: Require-Bundle: org.eclipse.jface.text; bundle-version="[3.8.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.jface.text; bundle-version="3.11.0.v20160505-1301"
org.eclipse.jface.text [255]
Unresolved requirement: Require-Bundle: org.eclipse.jface; bundle-version="[3.5.0,4.0.0)"
-> Bundle-SymbolicName: org.eclipse.jface; bundle-
......
and so on for all modules. Is it a problem due java 1.7?
Thanks.
The line
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))"
is saying that Java 8 is required for the plugin.
There might also be other plugin version dependencies errors but you haven't included enough of the log to know for sure.
Note that the Birt download page says that Eclipse Neon (4.6) is required.

Eclipse fails after installing JBoss Tools

After installing JBoss Tools and restarting Eclipse IDE, I get following exception:
An error has occured. See the log file /home/abc/workspace/.metadata/.log
Eclipse does not start anymore. Can anybody help me, to fix this problem?
My setup:
Eclipse Version: Neon 2
OS: Fedora 25
JBoss Tools Update Site: https://download.jboss.org/jbosstools/updates/stable/
Log File:
!SESSION Wed Mar 22 21:41:43 CET 2017 ------------------------------------------
!ENTRY org.eclipse.equinox.launcher 4 0 2017-03-22 21:41:43.812
!MESSAGE Could not find extension: org.eclipse.wst.jsdt.nashorn.extension
!SESSION 2017-03-22 21:41:43.742 -----------------------------------------------
eclipse.buildId=4.6.2.v20170109-1424
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_CH
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.osgi 4 0 2017-03-22 21:41:44.473
!MESSAGE Bundle org.eclipse.wst.jsdt.nashorn.extension not found.
!ENTRY org.jboss.tools.vpe.cordovasim.eclipse 4 0 2017-03-22 21:41:45.447
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.vpe.cordovasim.eclipse [1051]
Unresolved requirement: Require-Bundle: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.0"
-> Bundle-SymbolicName: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.1.Final-v20140303-0018-B169"
org.jboss.tools.vpe.cordovasim [1050]
No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
!ENTRY org.eclipse.ui 2 0 2017-03-22 21:41:47.664
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-03-22 21:41:47.664
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
!ENTRY org.eclipse.ui 2 0 2017-03-22 21:41:48.283
!MESSAGE Warnings while parsing the commands from the 'org.eclipse.ui.commands' and 'org.eclipse.ui.actionDefinitions' extension points.
!SUBENTRY 1 org.eclipse.ui 2 0 2017-03-22 21:41:48.283
!MESSAGE Commands should really have a category: plug-in='net.sf.eclipsecs.ui', id='CheckstylePlugin.PurgeCaches', categoryId='net.sf.eclipsecs'
!ENTRY org.jboss.tools.xulrunner.initializer 2 0 2017-03-22 21:41:50.274
!MESSAGE Could not resolve module: org.jboss.tools.xulrunner.initializer [1068]
Unresolved requirement: Fragment-Host: org.eclipse.swt
Unresolved requirement: Fragment-Host: org.eclipse.swt
!ENTRY org.jboss.tools.vpe.cordovasim.eclipse 2 0 2017-03-22 21:41:50.281
!MESSAGE Could not resolve module: org.jboss.tools.vpe.cordovasim.eclipse [1051]
Unresolved requirement: Require-Bundle: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.0"
-> Bundle-SymbolicName: org.jboss.tools.vpe.cordovasim; bundle-version="3.5.1.Final-v20140303-0018-B169"
org.jboss.tools.vpe.cordovasim [1050]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
!ENTRY org.jboss.tools.foundation.security.linux 2 0 2017-03-22 21:41:50.282
!MESSAGE Could not resolve module: org.jboss.tools.foundation.security.linux [997]
Unresolved requirement: Fragment-Host: org.eclipse.equinox.security; bundle-version="1.1.100"
Unresolved requirement: Fragment-Host: org.eclipse.equinox.security; bundle-version="1.1.100"
!ENTRY org.jboss.tools.vpe.cordovasim 2 0 2017-03-22 21:41:50.282
!MESSAGE Could not resolve module: org.jboss.tools.vpe.cordovasim [1050]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"] because it is exposed to package 'org.eclipse.jetty.continuation' from resources org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"] and org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"] via two dependency chains.
Chain 1:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.continuation)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="9.4.0.M0"; osgi.identity="org.eclipse.jetty.continuation"]
Chain 2:
org.jboss.tools.vpe.cordovasim [osgi.identity; type="osgi.bundle"; version:Version="3.5.1.Final-v20140303-0018-B169"; osgi.identity="org.jboss.tools.vpe.cordovasim"]
require: (&(osgi.wiring.bundle=org.eclipse.jetty.servlets)(bundle-version>=8.1.3))
|
provide: osgi.wiring.bundle; bundle-version:Version="8.1.10.v20130312"; osgi.wiring.bundle="org.eclipse.jetty.servlets"
org.eclipse.jetty.servlets [osgi.identity; type="osgi.bundle"; version:Version="8.1.10.v20130312"; osgi.identity="org.eclipse.jetty.servlets"]
import: (&(osgi.wiring.package=org.eclipse.jetty.server)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package=org.eclipse.jetty.server; uses:=org.eclipse.jetty.continuation
org.eclipse.jetty.server [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.server"]
import: (&(osgi.wiring.package=org.eclipse.jetty.continuation)(&(version>=8.1.0)(!(version>=9.0.0))))
|
export: osgi.wiring.package: org.eclipse.jetty.continuation
org.eclipse.jetty.continuation [osgi.identity; type="osgi.bundle"; version:Version="8.1.14.v20131031"; osgi.identity="org.eclipse.jetty.continuation"]
!ENTRY org.eclipse.osgi 4 0 2017-03-22 21:41:50.282
!MESSAGE Application error
!STACK 1
org.eclipse.e4.ui.css.core.sac.ParserNotFoundException: java.lang.ClassCastException: org.apache.batik.css.parser.Parser cannot be cast to org.w3c.css.sac.Parser
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.getParser(AbstractCSSParser.java:149)
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.parseStyleSheet(AbstractCSSParser.java:58)
at org.eclipse.e4.ui.css.core.impl.engine.AbstractCSSEngine.parseStyleSheet(AbstractCSSEngine.java:183)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:428)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:389)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.setTheme(ThemeEngine.java:381)
at org.eclipse.e4.ui.css.swt.internal.theme.ThemeEngine.restore(ThemeEngine.java:568)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.setCSSTheme(PartRenderingEngine.java:1399)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.initializeStyling(PartRenderingEngine.java:1292)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1026)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
Caused by: java.lang.ClassCastException: org.apache.batik.css.parser.Parser cannot be cast to org.w3c.css.sac.Parser
at org.eclipse.e4.ui.css.core.impl.sac.SACParserFactoryImpl.makeParser(SACParserFactoryImpl.java:49)
at org.eclipse.e4.ui.css.core.sac.SACParserFactory.makeParser(SACParserFactory.java:36)
at org.eclipse.e4.ui.css.core.impl.dom.parsers.AbstractCSSParser.getParser(AbstractCSSParser.java:139)
... 30 more
The version of the JBoss Tools, which you get from this update site is from 2014. It's too old. The correct update site link is: http://download.jboss.org/jbosstools/neon/stable/updates/.
By now the latest stable version is 4.4.3.Final: http://tools.jboss.org/downloads/jbosstools/neon/4.4.3.Final.html
Other versions (development and nightly) you can find here: http://tools.jboss.org/downloads/jbosstools/neon/index.html
The best and easiest way to install jbosstools plugins to Eclipse is by using Eclipse Marketplace plugin: https://marketplace.eclipse.org/content/jboss-tools.
Old, but still actual video with instructions of how to install JBoss Tools via Eclipse Marketplace plugin: http://tools.jboss.org/downloads/installation.html
I've updated the README.html on the /updates/stable page [1] to point users to the latest JBoss Tools releases [2].
[1] http://download.jboss.org/jbosstools/updates/stable/
[2] http://tools.jboss.org/downloads/jbosstools/
Also updated the composite*.xml files in [1] to point to the Neon release, though this URL should not be considered current at all times (as you saw, it was pointing you at the JBoss Tools 4.1 release based on Eclipse Kepler, not the 4.4 release based on Neon).

com.worklight.studio.plugin thread hangs on eclipse startup if existing worklight projects in workspace

I have eclipse Juno and the IBM Worklight studio plugin v5.0.5 installed. The worklight documentation specific that eclipse Juno is supported, but if I create a worklight project and then close eclipse, and then try to start it up again a thread hangs on startup loading things from com.worklight.studio.plugin and I end up having to kill eclipse since it just hangs on the loading screen. It is not the same package loaded everytime either that it hangs on, it seems to be random. Here is a stacktrace from when it happened once:
!MESSAGE While loading class "com.worklight.studio.plugin.classpaths.ServerAPIContainer", thread "Thread[org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor,1,main]" timed out waiting (5000ms) for thread "Thread[Worker-0,5,main]" to finish starting bundle "com.worklight.studio.plugin_5.0.5.20121129-1027 [882]". To avoid deadlock, thread "Thread[org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor,1,main]" is proceeding but "com.worklight.studio.plugin.classpaths.ServerAPIContainer" may not be fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/com.worklight.studio.plugin_5.0.5.20121129-1027/" by thread "Worker-0".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1088)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464)
...
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
... 45 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1088)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)
at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)
...
eclipse.buildId=M20130204-1200
java.version=1.7.0_15
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
It's a very long stack trace so I just included the parts I thought were relevant above. I can start eclipse again by deleting the worklight projects from my workspace, but this means I can only ever work on a project for a single session. I've seen other posts about this issue, but they all give the same solution of just deleting the projects. Is there any more permanent solution to this issue?
Thanks,
Alex
Uninstall it and try the latest version, 5.0.6.1, however also make sure to delete from the Eclipse-workspace the WorklightServerHome folder (due to schema changes between 5.0.5 and 5.0.6.x).