Eclipse Community Forums: Newcomers » eclipse fails to start after windows laptop restart

Home » Newcomers » Newcomers » eclipse fails to start after windows laptop restart(issues with eclipse start after machine restart)

Show: Today's Messages :: Show Polls :: Message Navigator

eclipse fails to start after windows laptop restart [message #1856791]

Tue, 03 January 2023 04:41

bln prasad

Messages: 4
Registered: January 2023

Junior Member

Hi,
I'm consistently seeing the issue where eclipse fails to start after my (windows) laptop restart. ive moved to latest version jee-2022-12 but still issue is seen. the only way to recover is fresh install of same version.
it always throws this error on fail. can you please do the needful to fix same.
it creates 7 err log files. just pasting start and end of it below.

!SESSION 2023-01-03 09:38:40.644 -----------------------------------------------^M
eclipse.buildId=4.26.0.20221201-1200^M
java.version=17.0.5^M
java.vendor=Oracle Corporation^M
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IN^M
Framework arguments: -product org.eclipse.epp.package.jee.product^M
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product^M
^M
!ENTRY org.apache.felix.scr 4 0 2023-01-03 09:38:41.720^M
!MESSAGE FrameworkEvent ERROR^M
!STACK 0^M
org.osgi.framework.BundleException: Could not resolve module: org.apache.felix.scr [76]
Unresolved requirement: Import-Package: org.osgi.service.cm; version="[1.6.0,2.0.0)"; resolution:="optional"
Unresolved requirement: Import-Package: org.osgi.service.metatype; version="[1.2.0,2.0.0)"; resolution:="optional"
Unresolved requirement: Import-Package: org.osgi.service.component.runtime.dto; version="[1.5.0,2.0.0)"
-> Export-Package: org.osgi.service.component.runtime.dto; bundle-symbolic-name="org.osgi.service.component"; bundle-version="1.5.0.202109301733"; version="1.5.0"; uses:="org.osgi.dto,org.osgi.framework.dto"
org.osgi.service.component [889]
Unresolved requirement: Import-Package: org.osgi.util.promise; version="[1.0.0,2.0.0)"
-> Export-Package: org.osgi.util.promise; bundle-symbolic-name="org.osgi.util.promise"; bundle-version="1.2.0.202109301733"; version="1.2.0"; uses:="org.osgi.util.function"
org.osgi.util.promise [904]
Unresolved requirement: Import-Package: org.osgi.util.function; version="[1.1.0,2.0.0)"
Unresolved requirement: Import-Package: org.osgi.util.promise; version="[1.0.0,2.0.0)"
-> Export-Package: org.osgi.util.promise; bundle-symbolic-name="org.osgi.util.promise"; bundle-version="1.2.0.202109301733"; version="1.2.0"; uses:="org.osgi.util.function"
Unresolved requirement: Import-Package: org.osgi.service.component.runtime; version="[1.5.0,1.6.0)"
-> Export-Package: org.osgi.service.component.runtime; bundle-symbolic-name="org.osgi.service.component"; bundle-version="1.5.0.202109301733"; version="1.5.0"; uses:="org.osgi.framework,org.osgi.service.component.runtime.dto,org.osgi.util.promise"
Unresolved requirement: Import-Package: org.osgi.service.component; version="[1.5.0,1.6.0)"
-> Export-Package: org.osgi.service.component; bundle-symbolic-name="org.osgi.service.component"; bundle-version="1.5.0.202109301733"; version="1.5.0"; uses:="org.osgi.framework"
^M
at org.eclipse.osgi.container.Module.start(Module.java:463)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)^M
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1788)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)^M
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)^M
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)^M
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)^M
^M
!ENTRY org.eclipse.equinox.event 4 0 2023-01-03 09:38:41.749^M
!MESSAGE FrameworkEvent ERROR^M
!STACK 0^M
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.equinox.event [350]

*************** end **********************
^M
!ENTRY org.eclipse.osgi 4 0 2023-01-03 09:38:50.976^M
!MESSAGE Application error^M
!STACK 1^M
java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.datatools.connectivity.console.profile.StorageFileEditor, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel, org.eclipse.equinox.app.error, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaIndexer, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication.^M
at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:252)^M
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:33)^M
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)^M
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)^M
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)^M
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)^M
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)^M
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)^M
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)^M
at java.base/java.lang.reflect.Method.invoke(Method.java:568)^M
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)^M
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)^M
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)^M

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856793 is a reply to message #1856791]

Tue, 03 January 2023 06:26

Nitin Dahyabhai

Messages: 4493
Registered: July 2009

Senior Member

How was this originally installed, where was it installed to, and how are you reinstalling it?

_
Nitin Dahyabhai
Eclipse Web Tools Platform

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856794 is a reply to message #1856793]

Tue, 03 January 2023 06:49

bln prasad

Messages: 4
Registered: January 2023

Junior Member

i used "eclipse-inst-jre-win64 " installer to install for my java development by choosing "java EE IDE". it installs under my C:\user location.
for resinstall i use the same and installer chooses different folder by adding suffix ex: jee-2022-123, jee-2022-124 etc.

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856797 is a reply to message #1856794]

Tue, 03 January 2023 08:56

Ed Merks

Messages: 33226
Registered: July 2009

Senior Member

I wonder if some of the values in the eclipse.ini are off? Mine, for example, look like this

-startup
plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
--launcher.library
D:\Users\merks\.p2\pool\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.2.400.v20211117-0650
-product
org.eclipse.epp.package.committers.product
-showsplash
D:\Users\merks\.p2\pool\plugins\org.eclipse.epp.package.common_4.22.0.20211202-1200
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vm
C:\Program Files\Java\jdk-17.0.5+8\bin

You might also try to run eclipse.exe -clean to see if that helps.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856803 is a reply to message #1856797]

Tue, 03 January 2023 12:26

bln prasad

Messages: 4
Registered: January 2023

Junior Member

interesting. i never compared working and non working version. here is the difference. i've not updated it. so not sure from where its getting updated. Do you think thats what making difference? if yes then how do i control it?

Attachment: cfg.diff.png
(Size: 85.27KB, Downloaded 208 times)

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856814 is a reply to message #1856803]

Wed, 04 January 2023 08:09

Ed Merks

Messages: 33226
Registered: July 2009

Senior Member

Neither look correct to me. Nothing should be referencing something in your temp storage and if you are using a bundle pool (the default) the paths must be absolute referencing the location of the pool. It's as if you are using the temp storage as the bundle pool.

What's in your <home>/.p2/pools.info file? Mine contains 'D:\Users\merks\.p2\pool' hence the eclipse.ini entries pointing into that pool. In the installer, this is managed via the menu in the upper right's "Bundle Pools...".

If you have no working installations that you need to preserve, I'd suggest delete the <home>/.eclipse and <home>/.p2 and start a fresh clean installation without changing default locations...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856821 is a reply to message #1856814]

Wed, 04 January 2023 10:03

bln prasad

Messages: 4
Registered: January 2023

Junior Member

sure. I'll try this out and monitor for few days

Report message to a moderator

Re: eclipse fails to start after windows laptop restart [message #1856913 is a reply to message #1856821]

Mon, 09 January 2023 07:54

Sanjeev Rao

Messages: 2
Registered: January 2023

Junior Member

It looks like Eclipse is having a problem starting due to issues with some of the installed plugins. The error message mentions "unresolved requirements" for several packages, which suggests that the required packages are not being exported by the corresponding bundles.

One potential cause of this issue could be conflicts between different versions of the same package that are being imported and exported by different bundles. It could also be that some of the required packages are not being exported by any installed bundle at all.

One way to troubleshoot this issue would be to try and identify which bundles are exporting the required packages and whether there are any version conflicts. You can do this by looking at the "Import-Package" and "Export-Package" headers in the MANIFEST.MF files of the bundles.

You could also try disabling some of the installed plugins and seeing if that helps resolve the issue. If disabling a particular plugin helps, then that plugin may be causing the issue. In that case, you may want to try updating the plugin to the latest version or contacting the plugin's developers for further assistance.

Another potential solution could be to try cleaning the Eclipse configuration. You can do this by going to the Eclipse installation directory and deleting the "configuration" folder. This will reset the Eclipse configuration to the default, which might fix the issue. However, note that this will also reset any custom settings you have made in Eclipse, so you may need to set these up again after cleaning the configuration.

Let me know if this works for you.

Report message to a moderator

Previous Topic:	Cannot create CDS view for "Data Definition"
Next Topic:	Help color wont turn random

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Oct 12 22:27:50 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter