1. I had created IGNITE-7905 for this interaction with userVersion and
perhaps only ignite.Activate() issued from the client. I think it deals
with the code for Activate() using nested classes. The server decided that
it already had a version of the ignite code loaded, and wasn't going to
accept a different version from the client. My intent was to shoot down
only my code. When I stopped trying to activate the cluster from the
client, this symptom disappeared. And in 2.4 the need to try to activate
the cluster from the client went away.
2. -DH
3.
<https://issues.apache.org/jira/browse/IGNITE-7905>
On Thu, Mar 22, 2018 at 12:00 PM, ilya.kasnacheev <ilya.kasnach...@gmail.com
> wrote:
> Hello Dave!
>
> I suggest filling an issue agains Apache Ignite JIRA with this scenario and
> suggestions about how it should work after fix. Test case would be awesome.
>
> Regards,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
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 visit the Mimecast website.
