Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.lang.RuntimeException: Error initializing storage. at org.eclipse.osgi.internal.framework.EquinoxContainer. #13

Closed
rm5837 opened this issue Jun 7, 2022 · 4 comments
Labels
in:framework Issues related to the OSGi Framework implementation stale

Comments

@rm5837
Copy link

rm5837 commented Jun 7, 2022

We are using 3.10 OSGI framework .Customers are facing this issue in cluster nodes environment when trying to start the application and due to this issue the application is not starting.

When we use 3.5 OSGI framework in cluster nodes environment and customers are not facing the issue .

Whether this issue is addressed in any latest OSGI versions?

It will be very helpful if you can provide the workaround to resolve the issue .

Error while starting Framework:.java.lang.RuntimeException: Error initializing storage.
at org.eclipse.osgi.internal.framework.EquinoxContainer.(EquinoxContainer.java:77)
at org.eclipse.osgi.launch.Equinox.(Equinox.java:31)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:295)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.servletbridge.FrameworkLauncher.start(FrameworkLauncher.java:409)
at org.eclipse.equinox.servletbridge.BridgeServlet.init(BridgeServlet.java:99)
at javax.servlet.GenericServlet.init(GenericServlet.java:161)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:345)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1369)
at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:653)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:619)
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:426)
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:171)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:904)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:789)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:427)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:719)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1211)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1464)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:642)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:1042)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:795)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2279)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5536)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5662)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2284)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:436)
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:379)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:127)
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:985)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:524)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
Caused by: java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:208)
at java.io.DataInputStream.readInt(DataInputStream.java:398)
at org.eclipse.osgi.container.ModuleDatabase$Persistence.readWire(ModuleDatabase.java:1168)
at org.eclipse.osgi.container.ModuleDatabase$Persistence.load(ModuleDatabase.java:1028)
at org.eclipse.osgi.container.ModuleDatabase.load(ModuleDatabase.java:879)
at org.eclipse.osgi.storage.Storage.(Storage.java:146)
at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:86)
at org.eclipse.osgi.internal.framework.EquinoxContainer.(EquinoxContainer.java:75)
... 38 more

Regards,
Ravindra

@mickaelistria
Copy link
Contributor

Whether this issue is addressed in any latest OSGI versions?

Can't you check it by yourself?
Please try to build a standalone minimal story to reproduce this issue with latest release of Equinox and share it here.

@rm5837
Copy link
Author

rm5837 commented Jun 7, 2022

Hi ,

It is not the standalone application and It is web application using OSGI framework.
Our application is not a small application and it is difficult to replace the latest OSGI framework.
If you have any info related to the fix then please share with us . So that we will plan accordingly to upgrade to that version .
We are getting this issue in Cluster environment and not with the single node.

Regards,
Ravindra

@tjwatson
Copy link
Contributor

tjwatson commented Jun 7, 2022

If you have steps to reproduce we may have some luck in figuring out if it is fixed. 3.10 version of org.eclipse.osgi is very old at this point (2014). That is the first release of the Equinox framework after a major refactoring. Numerous fixes related to the framework module container and its persistent state have gone into the releases over the years. Regardless of this bug you will need to upgrade in order to be able to support LTS Java versions going forward. You have to move up to 3.12.0 org.eclipse.osgi to be able to run on Java 11 for example.

@laeubi laeubi transferred this issue from eclipse-equinox/equinox.framework Jun 16, 2022
@tjwatson tjwatson added the in:framework Issues related to the OSGi Framework implementation label Jun 16, 2022
@github-actions
Copy link

This issue has been inactive for 180 days and is therefore labeled as stale.
If this issue became irrelevant in the meantime please close it as completed. If it is still relevant and you think it should be fixed some possibilities are listed below.
Please read https://github.com/eclipse-equinox/.github/blob/main/CONTRIBUTING.md#contributing-to-eclipse-equinox for ways to influence development.

@github-actions github-actions bot added the stale label Dec 14, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in:framework Issues related to the OSGi Framework implementation stale
Projects
None yet
Development

No branches or pull requests

3 participants