Hello! I think that Ignite cannot unload old version of code, unless it is loaded with something like URI deployment module. Version checking is there but server can't get rid of old code if it's on classpath.
Regards, -- Ilya Kasnacheev пн, 17 сент. 2018 г. в 16:47, Dave Harvey <[email protected]>: > We have a client that uses the compute grid and message grid, as well as > the discovery API. It communicates with a server plugin. The cluster is > configured for CONTINUOUS peer class loading. In order to force the proper > code to be loaded for the compute tasks, we change the user version, e.g., > to 2. > > If the server sends the client a message on the message grid, using > java.lang.string, the client fails because the user version sent for > java.lang.string is 0, but the client insists on 2. > > How is this supposed to work? Our expectation was that the message grid > should not be affected by peer class loading settings. > > > > > *Disclaimer* > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by *Mimecast Ltd*, an innovator in Software as a > Service (SaaS) for business. Providing a *safer* and *more useful* place > for your human generated data. Specializing in; Security, archiving and > compliance. To find out more Click Here > <http://www.mimecast.com/products/>. >
