Re: Apache Ignite 1.7.0 Session caching issue with update session attributes

[Siva Annapareddy <si...@gmail.com>]

A crude solution is to use jdkmarshaller with <property
name="peerClassLoadingEnabled" value="true"/>  to identify all the LazyMap
objects included in the objects that are saved in session object. And change
the code to convert all the LazyMap objects to HashMap objects before saving
to the session object

This has worked 

Still Looking for an elegant solution 

Thanks for your time



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-1-7-0-Session-caching-issue-with-update-session-attributes-tp10220p10634.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite 1.7.0 Session caching issue with update session attributes

[vkulichenko <va...@gmail.com>]

I don't think there is more elegant solution in case you're using
JdkMarshaller. Enabling web session clustering is not always completely
transparent as you switch from local storage to distributed storage. With
JDK serialization it's required that all serialized classes implement
Serializable. However, as mentioned above, you should not have this issue
with BinaryMarshaller.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-1-7-0-Session-caching-issue-with-update-session-attributes-tp10220p10635.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.