It seems you are getting these exceptions from discovery or continuous processes (continuous queries, remote event listening, etc) which always uses JdkMarshaller for initialization. Are there any reasons you cannot mark your classes Serializable?
--Yakov 2015-07-09 20:55 GMT+03:00 zandider <[email protected]>: > Just recently upgraded to gridgain community fabric 1.1.4 (from 1.0.6), and > now am getting exceptions that certain objects we're storing in the grid > are > not marked as Serializable. > > Investigating further, it seems that the exception is stemming from > JdkMarshaller, whereas our config files have always specified > OoptimizedMarshaller, with requireSerializable set to false. I've verified > that our grid config files haven't changed, and that they're being used to > start the grid. > > Has there been an issue introduced loading the OptimizedMarshaller? I can > supply stack traces and files privately as needed. > > XML config file snippet > ... > <property name=marshaller"> > <bean > class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> > <property name="requireSerializable" value="false"/> > </bean> > </property> > .... > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Serialization-Exceptions-OptimizedMarshaller-not-being-used-tp626.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
