Re: [OT but still JSF]: Clustering, session replication, and database, too
Ok Romain. Im not sure if is tomee issue of msm issue, but i will send you a mail with the info to the tomee mailing list. 2013/10/20 Romain Manni-Bucau > Hi > > Tomcat/tomee session replication; memcached and custom session manager > (hazelcast) solutions are different. > > Typically in some of them you accept SPoF, not in others. The perf are not > the same too. Finally guarantees (synchronous or not persistence) can be > different too. > > Mark info were consistent but adapted to his apps I think. The "theorical" > solution is sometimes not enough... > > Was just to give some more inputs and dont believe in IT you have a single > solution. > > PS: if tomee clustering has issues please help us working on it on trunk > and tomee list > Le 20 oct. 2013 07:30, "José Luis Cetina" a écrit : > > > I have a early experience with a "mini cluster" 2 servers using tomee + > > memcached for session replication+ sticky session but using 1 only server > > for database (i mean i dont use db replication). My jsf apps (ear) are > > running in this mini cluster everithyng works fine except when i shutdown > > tomee for do a re deploy i always see an xhtml parser error. I could > never > > configure it session replication with tomcat. > > > > In your web apps just use distributable tag in web.xml and all other are > > configuration. You can use memcached to not only session replication even > > thougth for savr information of your app and with this you can share > > information between your nodes and with this you dont persist information > > that could be "transient". > > The result is incredible. > > > > As i sayed i could never configure session replication with tomcat, the > > only way i could do it is using memcached session replication. > > > > I dont know if anybody here have any experience with this. > > > > Regards Howard. > > El 19/10/2013 22:49, "Howard W. Smith, Jr." > > escribió: > > > > > I had a question or two, since I have been reading "Java Summit - > > Pitfalls > > > in EE"[1] provided by Mark Struberg while having a discussion on tomee > > user > > > list. > > > > > > The following page stated the following: > > > > > > Page 134 > > > Clustering > > > > > > * We use 'asymmetric clustering' > > > * use sticky sessions > > > * backup away the session to a memcached after each > > > request > > > * do not replicate the session over to other nodes! > > > * Session-Replication always in node pairs. > > > * only restore the session from the memcached if a failover > > > happened > > > * msm can be integrated into OWB: > > > http://code.google.com/p/memcached-session-manager/ > > > > > > Since it says, 'We use asymmetric clustering' and other suggestions > were > > > made, I found it appropriate to direct my question(s) to MyFaces 'JSF' > > user > > > list and committers. > > > > > > is there some type of blog (or two or three) available that discuss how > > to > > > properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, > > how > > > is the database replicated? I don't ever see database > cluster/replication > > > discussed by JSF developers; i recently had to search for database > > cluster > > > and saw 'replication', which is something i have not had to worry about > > > since my previous work involved database teams while i was doing > > > front-end/GUI software. > > > > > > now that i am doing java ee and jsf, i would love to know how to do > > > database clustering and/or replicating database while clustering JSF > > > webapp. Of course, right now, i only have one tomee which references > > > 'apache' derby (which is performing well, but I would love to get my > feet > > > wet and cluster my web app + database). i did search derby's mail list > > > archives and i learned about sequioa and HA-JDBC (High-Availability > > JDBC). > > > > > > i was hoping to get an answer from MyFaces 'JSF' > users/committers...based > > > on their experience. I think someone told me that they use mysql > > > (clustering); my preference is still 'apache' derby (smile). please > > > remember, i'm wondering if any blogs are available that discuss > > clustering > > > tomcat (preference = tomee) + JSF web app (with database) + memcached > > > session manager. > > > > > > Thomas has already started writing a blog[2] about this. I'm looking > > > forward to seeing sample config for it all (if available). :) > > > > > > [1] > > > > > > > > > http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf > > > > > > [2] > > > > > > > > > http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html > > > > > > -- --- *SCJA. José Luis Cetina* ---
Re: [OT but still JSF]: Clustering, session replication, and database, too
Hi Tomcat/tomee session replication; memcached and custom session manager (hazelcast) solutions are different. Typically in some of them you accept SPoF, not in others. The perf are not the same too. Finally guarantees (synchronous or not persistence) can be different too. Mark info were consistent but adapted to his apps I think. The "theorical" solution is sometimes not enough... Was just to give some more inputs and dont believe in IT you have a single solution. PS: if tomee clustering has issues please help us working on it on trunk and tomee list Le 20 oct. 2013 07:30, "José Luis Cetina" a écrit : > I have a early experience with a "mini cluster" 2 servers using tomee + > memcached for session replication+ sticky session but using 1 only server > for database (i mean i dont use db replication). My jsf apps (ear) are > running in this mini cluster everithyng works fine except when i shutdown > tomee for do a re deploy i always see an xhtml parser error. I could never > configure it session replication with tomcat. > > In your web apps just use distributable tag in web.xml and all other are > configuration. You can use memcached to not only session replication even > thougth for savr information of your app and with this you can share > information between your nodes and with this you dont persist information > that could be "transient". > The result is incredible. > > As i sayed i could never configure session replication with tomcat, the > only way i could do it is using memcached session replication. > > I dont know if anybody here have any experience with this. > > Regards Howard. > El 19/10/2013 22:49, "Howard W. Smith, Jr." > escribió: > > > I had a question or two, since I have been reading "Java Summit - > Pitfalls > > in EE"[1] provided by Mark Struberg while having a discussion on tomee > user > > list. > > > > The following page stated the following: > > > > Page 134 > > Clustering > > > > * We use 'asymmetric clustering' > > * use sticky sessions > > * backup away the session to a memcached after each > > request > > * do not replicate the session over to other nodes! > > * Session-Replication always in node pairs. > > * only restore the session from the memcached if a failover > > happened > > * msm can be integrated into OWB: > > http://code.google.com/p/memcached-session-manager/ > > > > Since it says, 'We use asymmetric clustering' and other suggestions were > > made, I found it appropriate to direct my question(s) to MyFaces 'JSF' > user > > list and committers. > > > > is there some type of blog (or two or three) available that discuss how > to > > properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, > how > > is the database replicated? I don't ever see database cluster/replication > > discussed by JSF developers; i recently had to search for database > cluster > > and saw 'replication', which is something i have not had to worry about > > since my previous work involved database teams while i was doing > > front-end/GUI software. > > > > now that i am doing java ee and jsf, i would love to know how to do > > database clustering and/or replicating database while clustering JSF > > webapp. Of course, right now, i only have one tomee which references > > 'apache' derby (which is performing well, but I would love to get my feet > > wet and cluster my web app + database). i did search derby's mail list > > archives and i learned about sequioa and HA-JDBC (High-Availability > JDBC). > > > > i was hoping to get an answer from MyFaces 'JSF' users/committers...based > > on their experience. I think someone told me that they use mysql > > (clustering); my preference is still 'apache' derby (smile). please > > remember, i'm wondering if any blogs are available that discuss > clustering > > tomcat (preference = tomee) + JSF web app (with database) + memcached > > session manager. > > > > Thomas has already started writing a blog[2] about this. I'm looking > > forward to seeing sample config for it all (if available). :) > > > > [1] > > > > > http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf > > > > [2] > > > > > http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html > > >
Re: [OT but still JSF]: Clustering, session replication, and database, too
I have a early experience with a "mini cluster" 2 servers using tomee + memcached for session replication+ sticky session but using 1 only server for database (i mean i dont use db replication). My jsf apps (ear) are running in this mini cluster everithyng works fine except when i shutdown tomee for do a re deploy i always see an xhtml parser error. I could never configure it session replication with tomcat. In your web apps just use distributable tag in web.xml and all other are configuration. You can use memcached to not only session replication even thougth for savr information of your app and with this you can share information between your nodes and with this you dont persist information that could be "transient". The result is incredible. As i sayed i could never configure session replication with tomcat, the only way i could do it is using memcached session replication. I dont know if anybody here have any experience with this. Regards Howard. El 19/10/2013 22:49, "Howard W. Smith, Jr." escribió: > I had a question or two, since I have been reading "Java Summit - Pitfalls > in EE"[1] provided by Mark Struberg while having a discussion on tomee user > list. > > The following page stated the following: > > Page 134 > Clustering > > * We use 'asymmetric clustering' > * use sticky sessions > * backup away the session to a memcached after each > request > * do not replicate the session over to other nodes! > * Session-Replication always in node pairs. > * only restore the session from the memcached if a failover > happened > * msm can be integrated into OWB: > http://code.google.com/p/memcached-session-manager/ > > Since it says, 'We use asymmetric clustering' and other suggestions were > made, I found it appropriate to direct my question(s) to MyFaces 'JSF' user > list and committers. > > is there some type of blog (or two or three) available that discuss how to > properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, how > is the database replicated? I don't ever see database cluster/replication > discussed by JSF developers; i recently had to search for database cluster > and saw 'replication', which is something i have not had to worry about > since my previous work involved database teams while i was doing > front-end/GUI software. > > now that i am doing java ee and jsf, i would love to know how to do > database clustering and/or replicating database while clustering JSF > webapp. Of course, right now, i only have one tomee which references > 'apache' derby (which is performing well, but I would love to get my feet > wet and cluster my web app + database). i did search derby's mail list > archives and i learned about sequioa and HA-JDBC (High-Availability JDBC). > > i was hoping to get an answer from MyFaces 'JSF' users/committers...based > on their experience. I think someone told me that they use mysql > (clustering); my preference is still 'apache' derby (smile). please > remember, i'm wondering if any blogs are available that discuss clustering > tomcat (preference = tomee) + JSF web app (with database) + memcached > session manager. > > Thomas has already started writing a blog[2] about this. I'm looking > forward to seeing sample config for it all (if available). :) > > [1] > > http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf > > [2] > > http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html >
[OT but still JSF]: Clustering, session replication, and database, too
I had a question or two, since I have been reading "Java Summit - Pitfalls in EE"[1] provided by Mark Struberg while having a discussion on tomee user list. The following page stated the following: Page 134 Clustering * We use 'asymmetric clustering' * use sticky sessions * backup away the session to a memcached after each request * do not replicate the session over to other nodes! * Session-Replication always in node pairs. * only restore the session from the memcached if a failover happened * msm can be integrated into OWB: http://code.google.com/p/memcached-session-manager/ Since it says, 'We use asymmetric clustering' and other suggestions were made, I found it appropriate to direct my question(s) to MyFaces 'JSF' user list and committers. is there some type of blog (or two or three) available that discuss how to properly cluster a tomcat/tomee/openwebbeans/myfaces JSF web app? also, how is the database replicated? I don't ever see database cluster/replication discussed by JSF developers; i recently had to search for database cluster and saw 'replication', which is something i have not had to worry about since my previous work involved database teams while i was doing front-end/GUI software. now that i am doing java ee and jsf, i would love to know how to do database clustering and/or replicating database while clustering JSF webapp. Of course, right now, i only have one tomee which references 'apache' derby (which is performing well, but I would love to get my feet wet and cluster my web app + database). i did search derby's mail list archives and i learned about sequioa and HA-JDBC (High-Availability JDBC). i was hoping to get an answer from MyFaces 'JSF' users/committers...based on their experience. I think someone told me that they use mysql (clustering); my preference is still 'apache' derby (smile). please remember, i'm wondering if any blogs are available that discuss clustering tomcat (preference = tomee) + JSF web app (with database) + memcached session manager. Thomas has already started writing a blog[2] about this. I'm looking forward to seeing sample config for it all (if available). :) [1] http://people.apache.org/~struberg/eesummit2013/Java%20EE%20Summit%20-%20pitfalls%20in%20EE.pdf [2] http://tandraschko.blogspot.com/2013/09/session-replication-clustering-failover.html
Re: [MyFaces 2.2] invoke @PreDestroy on (CDI) ViewScoped beans upon session expiration
On Fri, Oct 18, 2013 at 6:01 PM, Howard W. Smith, Jr. < smithh032...@gmail.com> wrote: > Based on these test results, @PreDestroy of MyFaces 2.2 CDI @ViewScoped > bean is executed via session invalidation and expiration. :) > > Great work and thank you, Leonardo, Gerhard, and MyFaces team! :) > When MyFaces 2.2.x is bundled with TomEE+ (snapshot), hopefully, I will remember to start using MyFaces 2.2.x CDI @ViewScoped bean. Until then, I will keep using MyFaces 2.1.12 and OmniFaces CDI @ViewScoped. i hope to do more MyFaces 2.2 testing, if/when i have bandwidth and/or use-case to do so. :)
