RE: [JBoss-user] N tier Load Balanced Environments - not your typica

[John Moore]

Based on what I'm going through now I'm imagining that the ease of configuration/deployment of the combined server is significant.  I am surprised about the mod_jk option, I thought I saw an earlier benchmark that showed it was a significantly slower configuration.  Will give the test a shot to see what we come up with.  Will post to the group what we find.   In terms of keeping them separated, Piranha (linux lvs/nanny) is setup for the http side.  I know that I'll have to balance the naming service port.  What port does the client connect to the EJB server on?  The likely ports I see are 4444, 1056, 1055, 8083 and 1052, assuming it doesn't go back in on 1099.    Then to figure out how to make lvs/nanny think that the service think that the load balanced ports are working when it uses send and expect strings to determine what is alive.  Works great for http traffic where I can send a get string and get back clear text.   John   -----Original Message----- From: Vinay Menon [mailto:[EMAIL PROTECTED]] Sent: Friday, May 04, 2001 12:48 PM To: JBOSS Subject: Re: [JBoss-user] N tier Load Balanced Environments - not your typica John,       A couple of thoughts. Separating the Tomcat and the JBoss stack will cost in terms of serialization.... but your set up is going to be typical of most production systems. But if you have no solid reason for not separating them, do not! Also, have you benchmarked the Tomcat server's http server? The 8080 one. We found it very slow. Apache-mod_jk-Tomcat seemed to give a good response time. The optimized vs non-optimized test that ships with JBoss should give an idea of separating the Tomcat and JBoss stacks.     Just setting the ball rolling!   Vinay  ----- Original Message ----- From: John Moore Sent: Friday, May 04, 2001 7:34 PM To: jBoss Users (E-mail) Subject: [JBoss-user] N tier Load Balanced Environments - not your typica We are in the mist of development of a new product that will use JBoss as the EJB server.   Now I know that a load balanced solution is not available through the container.  Our plan, at the moment, is to have a balancer in front of the web tier and another in front of the EJB tier; we were not *currently* planning to run them on the same servers (Tomcat/JBoss).    I am setting up the environment now and was looking for any recommendations before I go too far down the road.  Has anyone used hardware/software balancers to sit in front of multiple EJB servers?   What did you do if the balancer crashes?(I'm pretty sure I'm going to add code on the web tier for other naming server(s) when the failover balancer kicks in). Are there any benchmarks that show the cost/performance of a combined server (e.g. Tomcat/JBoss)  vs.  distributed across web and application server tiers? On a related topic: Is there a design/plan for the new naming service to permit a consolidated view of all containers so that one can identify all of the places that a particular bean is executing?   Will that data be shared in a master-slave or peer-peer configuration?   What about a backing data store (ldap, db, ?) If there is a plan I'd be happy to take a look at the jnp stuff and see what I can do. John John Moore [mailto:[EMAIL PROTECTED]] PDSI 625 The City Drive Suite 190 Orange, CA 92868 800-850-7374 Get your FREE download of MSN Explorer at http://explorer.msn.com