You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Xander Uiterlinden (JIRA)" <ji...@apache.org> on 2019/02/19 07:58:00 UTC
[jira] [Created] (IGNITE-11351) Basic "Starting Ignite inside an
OSGi container" doesn't work
Xander Uiterlinden created IGNITE-11351:
-------------------------------------------
Summary: Basic "Starting Ignite inside an OSGi container" doesn't work
Key: IGNITE-11351
URL: https://issues.apache.org/jira/browse/IGNITE-11351
Project: Ignite
Issue Type: Bug
Components: osgi
Affects Versions: 2.7
Environment: Apache Felix, JDK 1.8
Reporter: Xander Uiterlinden
Attachments: ignite-osgi-patch.diff
When running the example from [https://apacheignite.readme.io/v1.5/docs/osgi-starting-inside-a-container] you're getting the following error.
Failed to start Ignite via OSGi Activator [errMsg=Failed to find empty constructor for class: o.a.i.i.processors.platform.websession.PlatformDotNetSessionLockResult]class
Looking at the codebase this class does indeed not have an empty constructor.
When adding that, you'll be running into the next issue which is a classloader issue. Ignite needs to be started with the correct context classloader for it to start successfully.
Please find the attached patch that resolves both problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)