SSE core task scheduler startup problem in eclipse

Patel Harsh 0
Viewed 148

Whenever I'm launching my eclipse IDE with my project workspace, there is one popup window showing some internal error with the task scheduler. I'm attaching the picture of that popup window here. https://i.stack.imgur.com/KycYG.jpg

My project is all in java language and also uses spring boot in it.

The error says something like

An internal error occurred during: "SSE core task scheduler startup"

Sorry I'm not able to add a direct image for this as Stack overflow is not allowing me to do that.

startup-error eclipse spring spring-boot java
2 Answers

Running with temurin-18.jdk on MacOS, stack below.

Offending call to new StringTokenizer(..):

https://git.eclipse.org/r/plugins/gitiles/sourceediting/webtools.sourceediting/+/refs/heads/master/core/bundles/org.eclipse.wst.sse.core/src/org/eclipse/wst/sse/core/utils/StringUtils.java#777

Looks like an errant import from com.ibm instead of java.util.StringTokenizer:

https://git.eclipse.org/r/plugins/gitiles/sourceediting/webtools.sourceediting/+/refs/heads/master/core/bundles/org.eclipse.wst.sse.core/src/org/eclipse/wst/sse/core/utils/StringUtils.java#27

import com.ibm.icu.util.StringTokenizer;

Stack:

!ENTRY org.eclipse.core.jobs 4 2 2022-09-22 08:11:42.471 !MESSAGE An internal error occurred during: "SSE core task scheduler startup". !STACK 0 java.lang.NoClassDefFoundError: com/ibm/icu/util/StringTokenizer at org.eclipse.wst.sse.core.utils.StringUtils.unpack(StringUtils.java:777) at org.eclipse.wst.sse.core.internal.tasks.TaskScanningJob.getScannedProjects(TaskScanningJob.java:295) at org.eclipse.wst.sse.core.internal.tasks.TaskScanningJob.projectHasNotBeenFullyScanned(TaskScanningJob.java:152) at org.eclipse.wst.sse.core.internal.tasks.TaskScanningJob.addProject(TaskScanningJob.java:118) at org.eclipse.wst.sse.core.internal.tasks.TaskScanningScheduler.enqueue(TaskScanningScheduler.java:137) at org.eclipse.wst.sse.core.internal.tasks.TaskScanningScheduler.startup(TaskScanningScheduler.java:117) at org.eclipse.wst.sse.core.internal.SSECorePlugin.lambda$0(SSECorePlugin.java:96) at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:166) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: java.lang.ClassNotFoundException: com.ibm.icu.util.StringTokenizer cannot be found by org.eclipse.wst.sse.core_1.2.800.v202207121749 at org.eclipse.osgi.internal.loader.BundleLoader.generateException(BundleLoader.java:541) at org.eclipse.osgi.internal.loader.BundleLoader.findClass0(BundleLoader.java:487) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:416) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:168) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) ... 9 more

userraCM0

For me, Eclipse was almost working until these two updates occurred:

Mylyn WikiText  3.0.43.202209151832 org.eclipse.mylyn.wikitext_feature.feature.group    Eclipse Mylyn

M2E - Maven Integration for Eclipse 2.0.5.20220912-1211 org.eclipse.m2e.feature.feature.group   Eclipse.org - m2e

The StringTokenizer error appeared immediately after Eclipse restarted.

(I emphasize almost because M2E was never copying the Maven Dependencies into the WEB-INF/lib of my configured server.)

Thad0
Related