Hello! - Have you tried to explicitly do setAttribute(key, changedObject) during request handling? - Do you have binary or POJO session store? This is controlled by org.apache.ignite.cache.websession.WebSessionFilter#WEB_SES_KEEP_BINARY_PARAM = true|false. Can you try both? - Can you enable DEBUG logging, see if you observe messages like "Session binary attributes updated" or "Session attributes updated"?
Regards, -- Ilya Kasnacheev ср, 26 дек. 2018 г. в 15:52, Rout, Biswajeet <biswajeet.r...@verizon.com>: > Hi Ilya, > > This is a real enterprise project, so I can not share any kind of code or > logs. > > In my project, I am doing a lot of update to an Object which is inside the > session. > I can see the websession is present in the Cache, but the updates done by > me at later point of time inside the code is not persisted into the cache. > > How do I persist the updated web session? > Should Ignite take care of it automatically? or Do I need to perform > something in order to save it in web session cache? > > Regards, > Biswajeet > > On Wed, Dec 26, 2018 at 6:13 PM Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > >> Hello! >> >> When you do getAttribute/setAttribute/removeAttribute on web session, it >> should be updated at the end of requedt. >> >> Do you have reproducer for this kind of behavior? >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> ср, 26 дек. 2018 г. в 13:46, Rout, Biswajeet <biswajeet.r...@verizon.com >> >: >> >>> Hi, >>> I did not get your question. >>> >>> I have two independent app servers under one load balancer which is in >>> AWS. the Ignite nodes are getting discovered using the S3 discovery >>> mechanism. >>> >>> I am pretty much sure that the nodes are getting discovered as well as >>> the session are getting shared across the servers. >>> But my problem is like, when I do some modification to the session, >>> those changes information is not cached. >>> >>> I have two questions in general: >>> >>> >>> - At which point of time the web session cache the session? >>> - Do ignite updates the web session cache, if I perform an update to >>> session? >>> >>> Regards, >>> Biswajeet Rout >>> >>> On Wed, Dec 26, 2018 at 4:02 PM Ilya Kasnacheev < >>> ilya.kasnach...@gmail.com> wrote: >>> >>>> Hello! >>>> >>>> Are you sure that your servers actually form an Ignite topology? Can >>>> you provide logs? >>>> >>>> Regards, >>>> -- >>>> Ilya Kasnacheev >>>> >>>> >>>> ср, 26 дек. 2018 г. в 10:07, Rout, Biswajeet < >>>> biswajeet.r...@verizon.com>: >>>> >>>>> ++ Ilya >>>>> >>>>> On Wed, Dec 26, 2018 at 12:35 PM Rout, Biswajeet < >>>>> biswajeet.r...@verizon.com> wrote: >>>>> >>>>>> Hi Ilya, >>>>>> >>>>>> I have two servers under a load balancer. I want my requests to be >>>>>> processed in any of these servers. >>>>>> When I keep on proceeding on my page, the requests may get processed >>>>>> in any of the servers. >>>>>> >>>>>> Answer to your questions: No I do not have any node loss and I have 1 >>>>>> backup node configured. >>>>>> >>>>>> Regards, >>>>>> Biswajeet >>>>>> >>>>>> On Mon, Dec 24, 2018 at 8:13 PM Ilya Kasnacheev < >>>>>> ilya.kasnach...@gmail.com> wrote: >>>>>> >>>>>>> Hello! >>>>>>> >>>>>>> Do you have a reproducer for this behavior? What do you mean by >>>>>>> "different server" here? Is there node loss? Do you have backups >>>>>>> configured? >>>>>>> >>>>>>> Regards, >>>>>>> -- >>>>>>> Ilya Kasnacheev >>>>>>> >>>>>>> >>>>>>> пн, 24 дек. 2018 г. в 15:57, Rout, Biswajeet < >>>>>>> biswajeet.r...@verizon.com>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> We are currently integrating Apache Ignite in our application to >>>>>>>> share sessions in a cluster. At this point, we can successfully share >>>>>>>> sessions between two servers, but there's one use case, which (seems) >>>>>>>> is >>>>>>>> not taken care by Ignite. >>>>>>>> >>>>>>>> In our application, we have a session object which is called >>>>>>>> *'SessiondataObject'*. This contains all the user information and >>>>>>>> all kinds of attributes are added to this object while the user browses >>>>>>>> through the application. >>>>>>>> >>>>>>>> We update the *'Sessiondataobject'* in various places. >>>>>>>> >>>>>>>> Without Apache Ignite, our session will contain the correct value. >>>>>>>> But when using Ignite, the Ignite *'WebSession'* object seems to >>>>>>>> work a bit different: when the control goes to a different server, it >>>>>>>> looks >>>>>>>> like the *'SessionDataObject'* does not have that updated >>>>>>>> information. >>>>>>>> >>>>>>>> how to make sure that the update to the *'SessionDataObject'* updates >>>>>>>> in the WebSession cache as well? >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> <http://www.verizon.com> >>>>>>>> >>>>>>>> Biswajeet >>>>>>>> Rout >>>>>>>> DTIX , DELPHI >>>>>>>> >>>>>>>> O +18136176308 | M 9703349977 >>>>>>>> biswajeet.r...@verizon.com >>>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> <http://www.verizon.com> >>>>>> >>>>>> Biswajeet >>>>>> Rout >>>>>> DTIX , DELPHI >>>>>> >>>>>> O +18136176308 | M 9703349977 >>>>>> biswajeet.r...@verizon.com >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> <http://www.verizon.com> >>>>> >>>>> Biswajeet >>>>> Rout >>>>> DTIX , DELPHI >>>>> >>>>> O +18136176308 | M 9703349977 >>>>> biswajeet.r...@verizon.com >>>>> >>>> >>> >>> -- >>> >>> <http://www.verizon.com> >>> >>> Biswajeet >>> Rout >>> DTIX , DELPHI >>> >>> O +18136176308 | M 9703349977 >>> biswajeet.r...@verizon.com >>> >> > > -- > > <http://www.verizon.com> > > Biswajeet > Rout > DTIX , DELPHI > > O +18136176308 | M 9703349977 > biswajeet.r...@verizon.com >
