Hello! I think you should avoid having final fields in classes sent over to nodes for execution. I also think that you should mark _ignite field with @IgniteInstanceResource (it might work anyway but this is more of Ignite way)
Regards, -- Ilya Kasnacheev пт, 28 сент. 2018 г. в 21:09, smurphy <smur...@trustwave.com>: > Hi Ilya, > > I don't think the errors are caused by the binary objects, but by having > custom objects in the EntryProcessor. Checkout the attached > FragmentAssignToScannerEntryProcessor.java. Instead of injecting the > BinaryFragmentConverter into FragmentAssignToScannerEntryProcessor, I moved > all the binary object code from BinaryFragmentConverter directly into > FragmentAssignToScannerEntryProcessor. > This works fine. > > Then I created the static FragmentAssignToScannerEntryProcessor.Tester > class, which has no binary objects, and added it as a member variable of > FragmentAssignToScannerEntryProcessor and that resulted in the same > IllegalArgumentException as before: "failed to read field [name=tester]" > > FragmentAssignToScannerEntryProcessor.java > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1317/FragmentAssignToScannerEntryProcessor.java> > > > stackTrace.txt > <http://apache-ignite-users.70518.x6.nabble.com/file/t1317/stackTrace.txt> > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
