We were using default set up for Web Sessions caching in Groovy Application. No specific Ignite code except reading default-config.xml that specifies : Cache Name Ignite Cluster IP Addresses to be discovered
Under Spring Security A session created is cached in Ignite JVMs. After Authentication, a new session is created and Session gets updated. During Session update, Application puts some Groovy objects in Session Object. Groovy Object contains fields without types specified. Some of the types seemed to have been implemented as LazyMap that is not serializable. Hence the Session stored on Ignite JVMs are not updated. Next time Application references the Session, it would not find necessary data in the Session retrived from Ignite JVMs On Thu, Jan 26, 2017 at 1:00 PM, Denis Magda-2 [via Apache Ignite Users] < [email protected]> wrote: > Binary Marshaller is used by default. So, don’t override marshaller in > your configuration. > > By the why are you trying to serialize this LazyMap? How does Ignite code > look like? > > - > Denis > > > On Jan 26, 2017, at 6:57 AM, Siva Annapareddy <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=10261&i=0>> wrote: > > > > Since OptimizedMarshaller is default we have run into issues: > > > > End of stream reached: java.io.ByteArrayInputStream@438f0960. > Stacktrace > > follows: > > Message: Failed to unmarshal object with optimized marshaller > > > > Hence, tried with jdkmarshaller and ran into Object Not Serializable > > > > We understand that Groovy 2.5.4 the default underlying Map is LazyMap > and > > that is not Serializable. > > > > We did not find org.apache.ignite.marshaller.binary.BinaryMarshaller in > > Ignite 1.7.0. Am I missing something? > > > > > > > > -- > > 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-tp10220p10257.html > > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Apache- > Ignite-1-7-0-Session-caching-issue-with-update-session- > attributes-tp10220p10261.html > To unsubscribe from Apache Ignite 1.7.0 Session caching issue with update > session attributes, click here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=10220&code=c2l2YS5hbm5hcGFyZWRkeUBnbWFpbC5jb218MTAyMjB8MTgyMjEwNzEwNw==> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- 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-tp10220p10265.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
