Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread 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

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread José Luis Cetina
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 rmannibu...@gmail.com Hi Tomcat/tomee session replication; memcached and custom session manager (hazelcast) solutions are different.

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Karl Kildén
Hello! I am also very interested in having more i.e. docs, examples and stuff for clustering across the tomee stack. The discussion came up on a jira some time ago and after that I asked Thomas to write a new post about it (First part was great!). For example this is something that sounds really

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Thomas Andraschko
Hey, JFYI: MyFaces+OWB on Tomcat with MSM is working fine. Don't know about TomEE. Regards, Thomas 2013/10/20 Karl Kildén karl.kil...@gmail.com Hello! I am also very interested in having more i.e. docs, examples and stuff for clustering across the tomee stack. The discussion came up on a

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Romain Manni-Bucau
@thomas: same on tomee + tomee has another integration for it, optimized for tomcat Le 20 oct. 2013 11:35, Thomas Andraschko andraschko.tho...@gmail.com a écrit : Hey, JFYI: MyFaces+OWB on Tomcat with MSM is working fine. Don't know about TomEE. Regards, Thomas 2013/10/20 Karl Kildén

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Thomas Andraschko
@romain do you have any article about it? Just for my interesst. What especially is optimized for tomcat? I may use TomEE in the future - if our customers allow this. 2013/10/20 Romain Manni-Bucau rmannibu...@gmail.com @thomas: same on tomee + tomee has another integration for it, optimized

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
smiling big... while I wrote OP (last night, my time), I did find Thomas's long discussion[1] with memcached-session-manager's committer/developer (Martin). and I remember Thomas said that Martin (the mail list) is 'very helpful', I think Thomas said that on primefaces forum. Romain, that

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
also, i'm still wondering about how database is replicated while clustering the app. On Sun, Oct 20, 2013 at 5:34 AM, Thomas Andraschko andraschko.tho...@gmail.com wrote: JFYI: MyFaces+OWB on Tomcat with MSM is working fine.

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
romain, i have recognized and (gmail) star'red the mail list topics related to tomee clustering. have not tried yet, but i don't see (any) mention of how database is replicated while clustering tomee. On Sun, Oct 20, 2013 at 2:11 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS: if tomee

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
interesting response, Jose', thanks! for some time, I thought that it might be best to have separate server (tomee + @EJB/DTO's + tomcat's jdbc + database) which is/becomes the database tier. I guess I need to learn how to do/make remote calls to EJB server from JSF web layer like you are doing.

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
On Sun, Oct 20, 2013 at 7:07 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: hmmm, avoid database replication. honestly, I think HA-JDBC[1] (clustering the database) is all I really need, because my app is quite fast, and only bottleneck is database layer. I have seen David Blevins or

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Mark Struberg
DB replication basically works with the transaction log (IBM DB/2 terminology, in Oracle it's called transfer tables). Each update/insert/delete statement gets written into a file and you can pick this file up from another node. This secondary node then does exactly the same like the first

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Mark Struberg
Try to avoid any remoting. Regardless whether remote EJB or even worse SOAP. The power it takes to transfer all your state to a different node is usually more than it takes to render your JSF pages. If you have performance issues then rather scale-out by adding another node and have a haproxy

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
interesting response, (and thanks) Mark! glad you feel that way about clustering (expensive and not worth the hassle), and scaling out the database for expensive queries/searches is definitely what I want, because I really think the tomee+ stack is performing very very well on my fast hardware.

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Mark Struberg
With Caching I meant stuff like all the things which do not change often. There is a big difference between 'almost static' data and between 'living data'. E.g. the User data can surely be cached for 30 minutes. How often do you add or change a new user in your system? Same for e.g. an amazon

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
On Sun, Oct 20, 2013 at 8:17 AM, Mark Struberg strub...@yahoo.de wrote: This can also be very helpful to 'scale out' in case you need performance: All write stuff is only performed on the master node, but expensive queries/searches might be performed on the n replication nodes. Of course

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
wow, good point. I don't ever create new users in app. currently, the app is only 'for-office-use' only, but some day, i'm hoping the app will serve the customers of the business (and endusers have already mentioned some/different requirements where customers can login and do some stuff in the

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
just remembered-and-revised 2nd question, below... On Sun, Oct 20, 2013 at 8:35 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Sun, Oct 20, 2013 at 8:17 AM, Mark Struberg strub...@yahoo.de wrote: This can also be very helpful to 'scale out' in case you need performance: All

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread José Luis Cetina
By the way im not using remote calls. All my apps are in the same ear with this i can inject my ejb local interface for calling methods in ejb. El 20/10/2013 07:49, Howard W. Smith, Jr. smithh032...@gmail.com escribió: just remembered-and-revised 2nd question, below... On Sun, Oct 20, 2013 at

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
Hmmm, i thought you said that you have EAR on one server and database on separate server. are you running 2 tomee on same server; one tomee = EAR, another tomee = database? On Sun, Oct 20, 2013 at 11:52 AM, José Luis Cetina maxtorz...@gmail.comwrote: By the way im not using remote calls. All

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread José Luis Cetina
Ear with all my apps in each server (2 server each with their own ear) then each server insert/read in another unique db server. El 20/10/2013 16:09, Howard W. Smith, Jr. smithh032...@gmail.com escribió: Hmmm, i thought you said that you have EAR on one server and database on separate server.

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
so, db server is on a separate machine/server on the network, and each EAR is referencing the (one) db server via IP address? also, do you have an embedded db server (running inside of tomee and using tomcat jdbc pooling) or network db server/engine? On Sun, Oct 20, 2013 at 5:32 PM, José Luis

ist außer Haus.

2013-10-20 Thread Klaus SCHUSTER
Ich bin seit 21.10.2013 nicht im Büro. Ich kehre zurück am 22.10.2013. In dringenden Fällen kontaktieren Sie bitte für den Bereich Elba Webcare Hr. Holzlechner (eMail.: holzlech...@racon-linz.at - DW: 8918). Für Auswertungen Elbanet: Hr. Markus Nopp (eMail.: n...@racon-linz.at) Sowie für

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread José Luis Cetina
El 20/10/2013 19:34, Howard W. Smith, Jr. smithh032...@gmail.com escribió: so, db server is on a separate machine/server on the network, and each EAR is referencing the (one) db server via IP address? Yes 2 tomee instances each in separete server point to a third server that only serve as db

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
interesting. thanks Jose' On Sun, Oct 20, 2013 at 9:03 PM, José Luis Cetina maxtorz...@gmail.comwrote: El 20/10/2013 19:34, Howard W. Smith, Jr. smithh032...@gmail.com escribió: so, db server is on a separate machine/server on the network, and each EAR is referencing the (one) db

Re: [OT but still JSF]: Clustering, session replication, and database, too

2013-10-20 Thread Howard W. Smith, Jr.
how many concurrent users is your app servingnormally or at peak times? earlier, i think you mentioned response time is quite fast. did you throw fast/high-performance hardware at db server, so db server responds fasts to queries/updates? do you have any expensive queries or updates...that