You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Rymsha (Jira)" <ji...@apache.org> on 2019/10/15 08:06:00 UTC
[jira] [Commented] (IGNITE-11351) Basic "Starting Ignite inside an
OSGi container" doesn't work
[ https://issues.apache.org/jira/browse/IGNITE-11351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951702#comment-16951702 ]
Sergey Rymsha commented on IGNITE-11351:
----------------------------------------
classloader issue is probably related to IGNITE-11662
> 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
> Priority: Major
> 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
(v8.3.4#803005)