You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "YuJue Li (Jira)" <ji...@apache.org> on 2020/11/04 11:07:00 UTC

[jira] [Updated] (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:all-tabpanel ]

YuJue Li updated IGNITE-13633:
------------------------------
    Summary: thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)  (was: When the thin client is used to call the ignite service（ use ignite-urideploy ）, ClassNotFound)

> 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
>            Priority: Critical
>         Attachments: ignite-deploy.zip
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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)