Re: Ignite Web Session Clustering with standalone node

[kay]

Thank you so much



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Web Session Clustering with standalone node

[Stephen Darlington]

The way you connect to a single server or a cluster is the same. You need to 
define a “finder” and the way you do that — well, one of the ways — is to 
configure it in an XML file 
(https://apacheignite.readme.io/docs/tcpip-discovery 
). In your example, that’s 
config/default-config.xml. For web session caching there’s no way to connect to 
a server with just an IP address and port. 

Regards,
Stephen

> On 1 Apr 2020, at 08:40, kay  wrote:
> 
> I'd like use web session clustering in my application.
> 
> I checked a page
> https://apacheignite-mix.readme.io/docs/web-session-clustering and There is
> no way to set standalone ignite nodes.. only like this ...
> 
> 
> 
>   IgniteConfigurationFilePath
>   config/default-config.xml 
> 
> how to set server ip:port at web.xml file?? or is there another way to
> connect to ignite server??
> 
> Thank you
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Web Session Clustering with standalone node

[kay]

I'd like use web session clustering in my application.

I checked a page
https://apacheignite-mix.readme.io/docs/web-session-clustering and There is
no way to set standalone ignite nodes.. only like this ...



   IgniteConfigurationFilePath
   config/default-config.xml 

how to set server ip:port at web.xml file?? or is there another way to
connect to ignite server??

Thank you



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Web Session Clustering

[slava.koptilin]

Hello!

> our main project uses Jboss Seam 2.2.1.CR1, JSF 1.2_15, Facelets 1.1.14,
> Richfaces 
> 3.3.3, Hibernate 3.3.2, c3p0 0.9.1.2, Spring 3.1.3 and Servlet 2.5 (maybe
> we 
> can update the Servlet version, but not the others). 
Apache ignite has been officially tested with the following servlet
containers:
Apache Tomcat 7
Eclipse Jetty 9
Apache Tomcat 6
Oracle WebLogic >= 10.3.4

> As we're not using the most recent versions of those frameworks and there 
> are something like Seam contexts, do you think that our application is 
> suitable for Ignite Web Session Clustering? 
I think your application can be used with Ignite.
Anyway, the best way to know - is to try :)

Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Web Session Clustering

[whcmachado]

Hello!

First, I'm sorry for my late reply.

I didn't close my web browser between those tests.

But as you talked about cookies, I looked at the cookies on chrome developer
tools and for some unknow reason I had a cookie for '/' and
'/Ignite-WebApp'. I cleaned those cookies and everything works well now.

Now we're going to try to set up Ignite on our main project which uses
frameworks like Jboss Seam 2.2.1.CR1, JSF 1.2_15, Facelets 1.1.14, Richfaces
3.3.3, Hibernate 3.3.2, c3p0 0.9.1.2, Spring 3.1.3 and Servlet 2.5 (maybe we
can update the Servlet version, but not the others).

As we're not using the most recent versions of those frameworks and there
are sommething like Seam contexts, do you think that our application is
suitable for Ignite Web Session Clustering?

Do you have any advice?

I really appreciate any help you can provide.

Thank you!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Web Session Clustering

[Ilya Kasnacheev]

Hello!

May it be so that you lost the session cookie during redeploy of war to
webapps folder?
For example, you could close browser session and start a new one.

This will lead to allocation of new session with counter at zero, while the
previous counter still exists but now inaccessible?

Can you check that you are actually using the same cookie before and after
webapp restart?


-- 
Ilya Kasnacheev

2017-10-20 16:32 GMT+03:00 whcmachado :

> Hi there,
>
> I'm trying to use Web Session Clustering. First, I got an example from the
> topic
> http://apache-ignite-users.70518.x6.nabble.com/Error-
> when-trying-to-configure-web-session-clustering-td6596.html
> where Vladislav PyatkovReply shared a Ignite-WebApp example
> http://apache-ignite-users.70518.x6.nabble.com/attachment/6714/0/Ignite-
> WebApp.zip.
>
> I did some changes to avoid some errors (I thought it happend by some
> Ignite's version changes)  as follows:
> Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
> property 'memoryMode'...
> Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
> property 'memoryMode'...
> Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
> property 'swapEnabled'...
>
> I also added a property on ignite-config.xml and set its value on web.xml
> as
> follows:
>
> 
>
> 
> IgniteWebSessionsGridName
> Ignite-WebApp.zip
>  t1412/Ignite-WebApp.zip>
> myGridName
> 
>
>
> I started 2 ignite nodes (apache-ignite-fabric-2.2.0) and a 3rd node that
> was the Ignite-WebApp on apache-tomcat-8.5.15. I was able to access the
> servlet on localhost (http://127.0.0.1:8080/Ignite-WebApp/gate) and after
> each refresh a counter increased its value.
>
> So, I stopped and restarted the tomcat and the counter kept its value and
> after each refresh the counter continued to increase. Great!
>
> Then, I just copied the same Ignite-WebApp.war to webapps folder (here a I
> didn't stop the tomcat), waited for the 3rd Ignite node restart, hit the
> servlet again, and that time the counter restarted its value.
>
> Is this a use case that the Ignite supports or am I by some lack of
> knowledge misunderstanding the Ignite's concepts?
>
> Can anyone help me?
>
> I really appreciate any help you can provide.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ignite Web Session Clustering

[whcmachado]

Hi there,

I'm trying to use Web Session Clustering. First, I got an example from the
topic
http://apache-ignite-users.70518.x6.nabble.com/Error-when-trying-to-configure-web-session-clustering-td6596.html
where Vladislav PyatkovReply shared a Ignite-WebApp example
http://apache-ignite-users.70518.x6.nabble.com/attachment/6714/0/Ignite-WebApp.zip.

I did some changes to avoid some errors (I thought it happend by some
Ignite's version changes)  as follows:
Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
property 'memoryMode'...
Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
property 'memoryMode'...
Caused by: org.springframework.beans.NotWritablePropertyException: Invalid
property 'swapEnabled'...

I also added a property on ignite-config.xml and set its value on web.xml as
follows:




IgniteWebSessionsGridName Ignite-WebApp.zip
  
myGridName



I started 2 ignite nodes (apache-ignite-fabric-2.2.0) and a 3rd node that
was the Ignite-WebApp on apache-tomcat-8.5.15. I was able to access the
servlet on localhost (http://127.0.0.1:8080/Ignite-WebApp/gate) and after
each refresh a counter increased its value.

So, I stopped and restarted the tomcat and the counter kept its value and
after each refresh the counter continued to increase. Great!

Then, I just copied the same Ignite-WebApp.war to webapps folder (here a I
didn't stop the tomcat), waited for the 3rd Ignite node restart, hit the
servlet again, and that time the counter restarted its value.

Is this a use case that the Ignite supports or am I by some lack of
knowledge misunderstanding the Ignite's concepts?

Can anyone help me?

I really appreciate any help you can provide.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Design question on the Ignite Web Session Clustering.

[Michael Cherkasov]

Hi,

I answered in SO, I copy it here:
"""
if you have a local cache for sessions and sticky sessions why do you need
to use ignite at all?

However, It's better to go with ignite, your app will have HA, if some node
is failed, the whole app still will work fine. I agree you should split app
cluster and ignite cluster, however, I think you shouldn't care about
connection problem about the server and client. This kind of problems
should lead to 500 error, would you emulate main storage if you DB go down
or you can't connect to it?
"""
Thanks,
Mikhail.

2017-09-07 20:12 GMT+03:00 Shrikant Patel <spa...@pdxinc.com>:

> Hi All,
>
>
>
> I have design question about Ignite web session clustering.
>
>
>
> I have springboot app with UI. It clustered app ie multiple instance of 
> springboot app behind the load balancer. I am using 
> org.apache.ignite.cache.websession.WebSessionFilter()to intercept request and 
> create\manage session for any incoming request.
>
>
>
> I have 2 option
>
>
>
> 1.  Embed the ignite node inside springboot app. So have these embedded 
> ignite node (on each springboot JVM) be part of cluster. This way request 
> session is replicated across the entire springboot cluster. On load balancer 
> I don’t have to maintain the sticky connection. The request can go to any app 
> in round robin or least load algorithm.
>
>
>
> Few considerations
>
> a.  Architect is simple. I don’t have worry about the cache being down 
> etc.
>
> b.  Now the cache being embedded, its using CPU and memory from app jvm. 
> It has potential of starving my app of resources.
>
>
>
> 2.  Have ignite cluster running outside of app JVM. So now I run client 
> node in springboot app and connect to main ignite cluster.
>
>
>
> Few considerations
>
>
>
> a.  For any reason, if the client node cannot connect to main ignite 
> cluster. Do I have to manage the session manually and then push those session 
> manually at later point to the ignite cluster??
>
> b.  If I manage session locally I will need to have sticky connection on 
> the load balancer. Which I want to avoid if possible.
>
>
>1. I am leaning to approach 2, but want to make it simple. So if
>   client node cannot create session (override 
> org.apache.ignite.cache.websession.WebSessionFilter())
>   it redirects user to page indicating the app is down or to another app 
> node
>   in the cluster.
>
>
>
>
>
> Are there any other design approach I can take?
>
> Am I overlooking anything in either approach?
>
>
>
> If you have dealt with it, please share your thoughts.
>
>
>
> Thanks in advance.
>
> Shri
>
>
> This e-mail and its contents (to include attachments) are the property of
> National Health Systems, Inc., its subsidiaries and affiliates, including
> but not limited to Rx.com Community Healthcare Network, Inc. and its
> subsidiaries, and may contain confidential and proprietary or privileged
> information. If you are not the intended recipient of this e-mail, you are
> hereby notified that any unauthorized disclosure, copying, or distribution
> of this e-mail or of its attachments, or the taking of any unauthorized
> action based on information contained herein is strictly prohibited.
> Unauthorized use of information contained herein may subject you to civil
> and criminal prosecution and penalties. If you are not the intended
> recipient, please immediately notify the sender by telephone at
> 800-433-5719 or return e-mail and permanently delete the original e-mail.
>

Re: Design question on the Ignite Web Session Clustering.

[Alison Mullan]

Hi Shri,

The very best way to get answers and advice on these kinds of questions is
to use the Apache Ignite Forum.
It is a very lively community and very supportive - register here
https://ignite.apache.org/

Let me know how you get on and if/when you would like to discuss
deployment/pricing/support issues for your end-users.
Best regards
Ali

On Thu, Sep 7, 2017 at 6:12 PM, Shrikant Patel <spa...@pdxinc.com> wrote:

> Hi All,
>
>
>
> I have design question about Ignite web session clustering.
>
>
>
> I have springboot app with UI. It clustered app ie multiple instance of 
> springboot app behind the load balancer. I am using 
> org.apache.ignite.cache.websession.WebSessionFilter()to intercept request and 
> create\manage session for any incoming request.
>
>
>
> I have 2 option
>
>
>
> 1.  Embed the ignite node inside springboot app. So have these embedded 
> ignite node (on each springboot JVM) be part of cluster. This way request 
> session is replicated across the entire springboot cluster. On load balancer 
> I don’t have to maintain the sticky connection. The request can go to any app 
> in round robin or least load algorithm.
>
>
>
> Few considerations
>
> a.  Architect is simple. I don’t have worry about the cache being down 
> etc.
>
> b.  Now the cache being embedded, its using CPU and memory from app jvm. 
> It has potential of starving my app of resources.
>
>
>
> 2.  Have ignite cluster running outside of app JVM. So now I run client 
> node in springboot app and connect to main ignite cluster.
>
>
>
> Few considerations
>
>
>
> a.  For any reason, if the client node cannot connect to main ignite 
> cluster. Do I have to manage the session manually and then push those session 
> manually at later point to the ignite cluster??
>
> b.  If I manage session locally I will need to have sticky connection on 
> the load balancer. Which I want to avoid if possible.
>
>
>1. I am leaning to approach 2, but want to make it simple. So if
>   client node cannot create session (override 
> org.apache.ignite.cache.websession.WebSessionFilter())
>   it redirects user to page indicating the app is down or to another app 
> node
>   in the cluster.
>
>
>
>
>
> Are there any other design approach I can take?
>
> Am I overlooking anything in either approach?
>
>
>
> If you have dealt with it, please share your thoughts.
>
>
>
> Thanks in advance.
>
> Shri
>
>
> This e-mail and its contents (to include attachments) are the property of
> National Health Systems, Inc., its subsidiaries and affiliates, including
> but not limited to Rx.com Community Healthcare Network, Inc. and its
> subsidiaries, and may contain confidential and proprietary or privileged
> information. If you are not the intended recipient of this e-mail, you are
> hereby notified that any unauthorized disclosure, copying, or distribution
> of this e-mail or of its attachments, or the taking of any unauthorized
> action based on information contained herein is strictly prohibited.
> Unauthorized use of information contained herein may subject you to civil
> and criminal prosecution and penalties. If you are not the intended
> recipient, please immediately notify the sender by telephone at
> 800-433-5719 <(800)%20433-5719> or return e-mail and permanently delete
> the original e-mail.
>



-- 
*Alison Mullan*
Business Development EMEA
GridGain systems
alison.mul...@gridgain.com
Phone: +44 7903 365482
www.gridgain.com

Design question on the Ignite Web Session Clustering.

[Shrikant Patel]

Hi All,

I have design question about Ignite web session clustering.


I have springboot app with UI. It clustered app ie multiple instance of 
springboot app behind the load balancer. I am using 
org.apache.ignite.cache.websession.WebSessionFilter()to intercept request and 
create\manage session for any incoming request.



I have 2 option



1.  Embed the ignite node inside springboot app. So have these embedded 
ignite node (on each springboot JVM) be part of cluster. This way request 
session is replicated across the entire springboot cluster. On load balancer I 
don't have to maintain the sticky connection. The request can go to any app in 
round robin or least load algorithm.



Few considerations

a.  Architect is simple. I don't have worry about the cache being down etc.

b.  Now the cache being embedded, its using CPU and memory from app jvm. It 
has potential of starving my app of resources.



2.  Have ignite cluster running outside of app JVM. So now I run client 
node in springboot app and connect to main ignite cluster.



Few considerations



a.  For any reason, if the client node cannot connect to main ignite 
cluster. Do I have to manage the session manually and then push those session 
manually at later point to the ignite cluster??

b.  If I manage session locally I will need to have sticky connection on 
the load balancer. Which I want to avoid if possible.

 *   I am leaning to approach 2, but want to make it simple. So if client 
node cannot create session (override 
org.apache.ignite.cache.websession.WebSessionFilter()) it redirects user to 
page indicating the app is down or to another app node in the cluster.


Are there any other design approach I can take?
Am I overlooking anything in either approach?

If you have dealt with it, please share your thoughts.

Thanks in advance.
Shri

This e-mail and its contents (to include attachments) are the property of 
National Health Systems, Inc., its subsidiaries and affiliates, including but 
not limited to Rx.com Community Healthcare Network, Inc. and its subsidiaries, 
and may contain confidential and proprietary or privileged information. If you 
are not the intended recipient of this e-mail, you are hereby notified that any 
unauthorized disclosure, copying, or distribution of this e-mail or of its 
attachments, or the taking of any unauthorized action based on information 
contained herein is strictly prohibited. Unauthorized use of information 
contained herein may subject you to civil and criminal prosecution and 
penalties. If you are not the intended recipient, please immediately notify the 
sender by telephone at 800-433-5719 or return e-mail and permanently delete the 
original e-mail.