You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2015/12/16 09:21:46 UTC
[jira] [Updated] (IGNITE-2091) Service Deployment: use service's
class String name instead of Class during deployment
[ https://issues.apache.org/jira/browse/IGNITE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-2091:
--------------------------------
Assignee: Artem Shutak
> Service Deployment: use service's class String name instead of Class during deployment
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-2091
> URL: https://issues.apache.org/jira/browse/IGNITE-2091
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Denis Magda
> Assignee: Artem Shutak
> Fix For: 1.6
>
>
> Every node that is a part of the cluster (including client nodes) checks whether a service should be deployed on it or not using its Class objects.
> In cases when a service is not supposed to be deployed on a node at all during its lifetime the node may not have services Class in its classpath and it will lead to ClassNotFoundException in {{GridServiceProcessor.AssignmentListener}}.
> AssignmentListener logic has to be modified in a way that a service's String class name will be used instead when it's needed to check whether the service must be deployed on a node or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)