[jira] [Updated] (IGNITE-13679) Entryprocessor cannot be hot deployed properly via UriDeploymentSpi

["Yaroslav Molochkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yaroslav Molochkov updated IGNITE-13679:
----------------------------------------
    Fix Version/s:     (was: 2.9.1)
                   2.10

> Entryprocessor cannot be hot deployed properly via UriDeploymentSpi
> -------------------------------------------------------------------
>
>                 Key: IGNITE-13679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13679
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.9
>            Reporter: YuJue Li
>            Priority: Critical
>             Fix For: 2.10
>
>         Attachments: ignite-deploy.zip
>
>
> Entryprocessor cannot be hot deployed properly via UriDeploymentSpi,the operation steps are as follows:
> 1.put jar in the specified folder of uriList;
> 2.Use example-deploy.xml,start two ignite nodes;
> 3.Use the DeployClient to deploy the service named "deployService";
> 4.Execute the test through ThickClientTest, and the result is correct;
> 5.Modify the code of DeployServiceImpl and DeployEntryProcessor, for example, change "Hello" to "Hi", then repackage it and put it into the specified folder of uriList;
> 6.Redeploy services by RedeployClient;
> 7.Execute the test again through ThickClientTest, and the result is incorrect,we will find that if the Entryprocessor accessed by the service is on another node, the Entryprocessor uses the old version of the class definition.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)