Develop Reference

Eclipse 202003 javaIO error during build project

Has anyone encountered with the following error during use Eclipse latest version: 202003?
I've downloaded it, update Java 1.8 to the latest Java version, start eclipse, add my PHP project and during the building or validation or DLTK indexing I got an Internal error.
Part from eclipse .log file:
!ENTRY org.eclipse.dltk.core.index.lucene 1 1 2020-04-30 16:33:01.599
!MESSAGE Recovering index storage: Y:\.metadata\.plugins\org.eclipse.dltk.core.index.lucene\index\4b74b979-df85-4fb0-bd11-ad91f89ae355\timestamps
!ENTRY org.eclipse.dltk.core.index.lucene 4 4 2020-04-30 16:33:01.617
!MESSAGE Index writer could not be created, index data might be corrupted.
!STACK 0
java.io.IOException: The request is not supported
at sun.nio.ch.FileDispatcherImpl.lock0(Native Method)
at sun.nio.ch.FileDispatcherImpl.lock(Unknown Source)
at sun.nio.ch.FileChannelImpl.tryLock(Unknown Source)
at java.nio.channels.FileChannel.tryLock(Unknown Source)
at org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:126)
at org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:41)
at org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:45)
at org.apache.lucene.store.SleepingLockWrapper.obtainLock(SleepingLockWrapper.java:84)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:729)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.createWriter(IndexContainer.java:139)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getWriter(IndexContainer.java:146)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getTimestampsWriter(IndexContainer.java:167)
at org.eclipse.dltk.internal.core.index.lucene.IndexRecovery.tryRecover(IndexRecovery.java:62)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getWriter(IndexContainer.java:149)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getTimestampsWriter(IndexContainer.java:167)
at org.eclipse.dltk.internal.core.index.lucene.IndexRecovery.tryRecover(IndexRecovery.java:62)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getWriter(IndexContainer.java:149)
at org.eclipse.dltk.internal.core.index.lucene.IndexContainer.getTimestampsWriter(IndexContainer.java:167)
........
I've no idea what is going wrong? WTF?
Java version is: jre1.8.0_251 and I've also tried reinstall previous java version what I used. This was: 1.8.0_202...but I got the same error again, and again, and again :(
I would like upgrade my Eclipse because of Symfony plugin...
Previous used java version: 1.8.0_191. I've reinstalled it and got back the error:
An internal error occurred during: "Build Modules".
java.lang.StackOverflowError
Building process stop at 49% :(
Can anybody help me?

Hi this is problem with DLTK 6.1 + PDT 7.1. We already fixed this: no more async and FS locks. Please update to recent snapshots or try Eclipse 2020-06 M2 or newest: https://www.eclipse.org/downloads/packages/release/2020-06/m2

Error: Eclipse 4.5 MARS NullPointerException (JUnit-Tests)

I do have a problem with Eclipse 4.5 when building a JUnit Test Class.
I can build all tests with the help of ant in its repository.
I think it is a configuration problem in Eclipse.
I already followed a lot of solutions in this forum:
Cleaning the path of eclipse itself
restarting eclipse
try to compile with JUnit3
try to compile with JUnit4
try another JRE
start the project in a different workspace
The reason why I haven't updated my Eclipse is because my company only uses Eclipse 4.5. So I can't accept an answer to update it.
The error log:
!ENTRY org.eclipse.core.jobs 4 2 2019-09-09 17:55:58.495
!MESSAGE An internal error occurred during: "Launching JUnitEntityDBUtility".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate$ClasspathLocalizer.localURL(JUnitLaunchConfigurationDelegate.java:429)
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate$ClasspathLocalizer.entryString(JUnitLaunchConfigurationDelegate.java:418)
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate$ClasspathLocalizer.addEntry(JUnitLaunchConfigurationDelegate.java:405)
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate$ClasspathLocalizer.localizeClasspath(JUnitLaunchConfigurationDelegate.java:396)
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate.getClasspath(JUnitLaunchConfigurationDelegate.java:373)
at org.eclipse.jdt.junit.launcher.JUnitLaunchConfigurationDelegate.launch(JUnitLaunchConfigurationDelegate.java:147)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Delete and recreate your JUnitEntityDBUtility launch configuration.
The stack trace can be found here and here. At the second finding you will find the explanation and a workaround by Moritz Eysholdt for your issue as follows (highlighting by me):
That NPE occurs if you execute a test's launch config in an Eclipse
that does not have the plugin org.eclipse.jdt.junit4.runtime.patch
installed when the launch config was created by an Eclipse that did
actually have org.eclipse.jdt.junit4.runtime.patch installed.
Workaround: Install org.eclipse.jdt.junit4.runtime.patch via the Xpect
update site or delete+recreate your launch configuration.
[...]

SonarQube Eclipse integration throwing NoSuchMethodError on Synchronize Issues

My maven project is properly associated with the project on our Sonar server. When I try to use the Eclipse "Analyze Project" option, it brings up a Problem Occurred window with
"'Synchronize issues' has encountered a problem.
An internal error occurred during: "Synchronize issues".
The details dropdown has
An internal error occurred during: "Synchronize issues".
org.apache.commons.lang.StringUtils.defaultIfBlank(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
If I look in the Eclipse log, I see
!ENTRY org.eclipse.core.jobs 4 2 2015-07-13 14:07:23.716
!MESSAGE An internal error occurred during: "Synchronize issues".
!STACK 0
java.lang.NoSuchMethodError: org.apache.commons.lang.StringUtils.defaultIfBlank(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
at org.sonar.ide.eclipse.core.internal.jobs.AnalyseProjectJob.(AnalyseProjectJob.java:88)
at org.sonar.ide.eclipse.core.internal.jobs.SynchronizeAllIssuesJob.scheduleIncrementalAnalysis(SynchronizeAllIssuesJob.java:100)
at org.sonar.ide.eclipse.core.internal.jobs.SynchronizeAllIssuesJob.run(SynchronizeAllIssuesJob.java:79)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Strangely enough, I installed the plugin on another machine today and Analyze Project works fine. Any ideas what could be causing this?

Worklight project upgrade error

I encountered a problem with Worklight project that is new technology for me.
Error while upgrading Worklight project from version 6.1.0.00-20131126-0630 to 6.1.0.01-20140821-0406 (also tried 6.1.0.02-21041216-0421). Error message:
Unexpected error during upgrade: java.lang.NullPointerException at com.worklight.upgrader.internal.Zipper.addFolderToZip(Zipper.java:190)
at com.worklight.upgrader.internal.Zipper.addFolderToZip(Zipper.java:202) at com.worklight.upgrader.internal.Zipper.addFolderToZip(Zipper.java:202)
at com.worklight.upgrader.internal.Zipper.addFolder(Zipper.java:106) at com.worklight.upgrader.internal.Zipper.addFolder(Zipper.java:91)
at com.worklight.upgrader.WLUpgradeEngine.backupCurrentProject(WLUpgradeEngine.java:645) at com.worklight.upgrader.WLUpgradeEngine.performUpgrade(WLUpgradeEngine.java:294)
at com.worklight.upgrader.WLUpgradeEngine.upgradeProject(WLUpgradeEngine.java:188) at com.worklight.studio.plugin.upgrader.WLUpgraderWorkspaceJob.runInWorkspace(WLUpgraderWorkspaceJob.java:127)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2 Build id: 20140224-0627
Win8.1 x64
Any help or suggestions are very appreciated.

All the builds you have tried are very, very old.
As an IBM customer you should download the latest available iFix for your Studio installation from IBM Fix Central. The latest should be from July 2015.
Please try again with that version.
You can also attempt to delete the wlBuildResources folder per the instructions in this question: Worklight - FWLST1040E: android build failed: java.io.FileNotFoundException
Finally, if this is still happening also with the latest available iFix (see above), provide a project that this issue is reproducible with so that it could be debugged.

Anypoint Studio 5.1.1 with empty properties view

I am running the new Version of AnypointStudio for win 64bit-5.1.0-201503171252 on a Windows 8.1 with Java 8.
If I click on a Element in the flow, I will see only:
.
I check the Eclipse Logfile (AnypointStudio\workspace\.metadata\.log) and find this error:
!ENTRY org.eclipse.e4.ui.workbench 4 2 2015-04-09 19:42:58.236
!MESSAGE Problems occurred when invoking code from plug-in: org.eclipse.e4.ui.workbench".
!STACK 0
java.lang.NoClassDefFoundError: org/mule/tooling/apikit/common/metadata/resolver/APIkitRouterInvokerMetadataResolver$1$1
at org.mule.tooling.apikit.common.metadata.resolver.APIkitRouterInvokerMetadataResolver$1.call(APIkitRouterInvokerMetadataResolver.java:65)
at org.mule.tooling.apikit.common.metadata.resolver.APIkitRouterInvokerMetadataResolver$1.call(APIkitRouterInvokerMetadataResolver.java:1)
at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:16)
I try this on different Workstation with the same error.
I search the missing class and found this file in the plugin folder:
AnypointStudio-for-win-64bit-5.1.0-201503171252\AnypointStudio\plugins\org.mule.tooling.apikit.common_1.6.1.201503121950\org\mule\tooling\apikit\common\metadata\resolver\APIkitRouterInvokerMetadataResolver$1$1.class

have you tried removing the older APIKit plugin and only installing the latest? It could be a conflict between the different versions.
HTH,
Eva