One followup question - how did you discover the answer to this, and how
would we discover answers to problems like these ourselves? I set
IGNITE_QUIET=false, and I increased logging level in
config/java.util.logging.properties and log4j2.xml on the client side to no
avail. Is following the tree of
Hey Pavel,
That does the trick! Interestingly, if I change the return value of the
entry processor to some other POJO and I register that POJO in the
BinaryConfiguration instead of LightsaberColor, the duplicate processing
still occurs. Perhaps this is related to the cache value rather than the
re
- Duplicate invocation happens due to automatic retry
for UnregisteredClassException caused by return value of type
LightsaberColor.
- Ignite handles the exception, registers the type automatically, and
re-runs the processor
- This only happens once, subsequent invocations are not duplicated
- To f
