You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Daradur (Jira)" <ji...@apache.org> on 2020/12/02 19:40:00 UTC
[jira] [Commented] (IGNITE-13633) thin clients cannot access the
Ignite Service deployed through UriDeploymentSpi(
java.lang.ClassNotFoundException)
[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242669#comment-17242669 ]
Vyacheslav Daradur commented on IGNITE-13633:
---------------------------------------------
[~alex_pl], the changes lgtm.
Let's getting new TC-bot visa just to be sure and I'll merge it.
> thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-13633
> URL: https://issues.apache.org/jira/browse/IGNITE-13633
> Project: Ignite
> Issue Type: Bug
> Components: managed services, thin client
> Affects Versions: 2.9
> Reporter: xingzhou
> Assignee: Aleksey Plekhanov
> Priority: Critical
> Fix For: 2.10
>
> Attachments: ignite-deploy.zip
>
> Original Estimate: 24h
> Time Spent: 3h
> Remaining Estimate: 21h
>
> When the thin client is used to call the ignite service( use ignite-urideploy ), the clientserviceinvokerequest will get the service classes, the local classloader is used, and the classes cannot be found. Therefore, the ignite-urideploy classloader should be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)