it will be extremelly clear in a couple of weeks, the possibility to **easily** cluster the servers with full web/j2ee stack will explode like an atom bomb in this field.
Not that the mail from kevin is out of touch, quite the contrary, it is just that it adresses too many points at once. Let us put some code out julian and let the code do the talking. This revolution will not be televised, will not be emailized, marc |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Julian |Gosnell |Sent: Wednesday, October 31, 2001 7:15 PM |To: [EMAIL PROTECTED]; [EMAIL PROTECTED] |Subject: [JBoss-user] Re: [jetty-discuss] Which is |preferred..Jetty/Jboss integrated, or separate JVMs.. | | |I guess this one's mine ! | |Here is my reasoning. | |Jetty is designed to be small lightweight and ideal for embedding. | |For this reason, it is the ideal candidate for the |web-and-ejb-container-in-one-jvm niche. | |This particular approach has benefits that appeal to a particular |user group. | |Their are cons to doing this - as you have pointed out. | |I did the in-vm integration because I thought that Jetty had a |real advantage here over other less suitable web-containers. | |There is no good reason why Jetty should not take them on in the |other ecological niche. It will just be more difficult because |Jetty does not carry a lot of the baggage containing all the bells |and whistles that other more heavyweight web-containers do |e.g. hot-deployers, nice configuration and reporting interfaces, etc... | |If you don't have a problem with Jetty's streamlined approach, |then I would be interested to hear about an extra-vm |integration. There are various pieces of the integration that I |would expect to be more awkward in doing this, such as security |and ENC (I'm not sure whether people expect these to be integrated |in extra-vm installations). | |Lastly, the clustering in JBoss 3.0 may offer an opportunity to |resolve your problem. | |I'm not aware yet if a JBoss3 cluster will always be a group of |homogenous nodes (i.e. all offering the same set of services), |or whether it may be comprised of heterogeneous nodes, e.g. |specialised web-facingvand db-facing tiers - perhaps the JBoss |architects can enlighten us ? | | |Jules | | |[EMAIL PROTECTED] wrote: | |> Hey all, |> |> I know alot of work has been done by Jules (and others?) to integrate |> Jetty and JBoss. I am curious though, what the real benfit is in |> terms of scalability? By this I mean, by using a single JVM you do |> gain a bit of performance, but you lose (or so I think) scalability |> in some regards. As J2EE is not dependent on, but based around |> multiple tiers, I would think it would be ideal to run Jetty in its |> own JVM, and JBoss in its own. Then, using jboss-client.jar (and |> other related files), access EJBs from Jetty as if it was any other |> client. In this manner, you can easily "scale" your site. You can do |> as I do, which is run Jetty by itself in its own JVM, and JBoss in |> its own JVM, then when the time comes move JBoss off to its own |> server (tier). Eventually, you'll want the ability to add one (or |> more) Jetty servers (for scaling web-tier requests) and one (or more) |> JBoss servers (for handling business logic/database needs). |> |> On that note, has anyone actually developed and/or deployed in an |> environment like this yet?? I am curious how you actually get one (or |> more) Jetty (or any servlet engine) servers to get EJB's from any one |> of many JBoss servers! If I recall correctly, I have to specify the |> specific IP of the server that JBoss is running on (or localhost if |> on the same server but in its own JVM) to gain access to its JNDI |> context to find the EJB. If this is the case, then how do you get EJB |> from multiple jboss servers each at different IPs in a way that |> properly loads the various servers? I assume the only way is to use a |> load balancer between all the JBoss servers (in their own tier), so |> that any Jetty front-end web-tier server only worries about the one |> load-balancer IP address to request EJB from, letting the load |> balancer direct the request to the proper EJB server to get the EJB |> reference. |> |> This is all assuming the same EJBs all reside on all the servers. I |> imagine it gets more complicated when you run some EJBs on a few |> servers, and other EJBs on a few other servers. I would think it best |> to use a "group" or "island" approach in this case, where you use a |> load balancer connected to some servers running the same set of EJBs, |> and another load balancer connected to some other servers running |> different EJBs. Then, the front-end web-apps just need to know what |> EJBs they want and what load-balancer IP to call to get those. |> |> So, is that how all this is done? Or is there a lot more that I am |> missing? At any rate, I am developing along the lines of Jetty in one |> JVM and JBoss in another JVM so that I am ready to deploy in a multi- |> tier environment for scalability purposes and would like to make sure |> I am doing it right. |> |> Thanks. |> |> ------------------------ Yahoo! Groups Sponsor ---------------------~--> |> Get your FREE VeriSign guide to security solutions for your web |site: encrypting transactions, securing intranets, and more! |> http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/CefplB/TM |> ---------------------------------------------------------------------~-> |> |> For the latest information about Jetty, please see http://jetty.mortbay. |> |> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ | | |_________________________________________________________ |Do You Yahoo!? |Get your free @yahoo.com address at http://mail.yahoo.com | | |_______________________________________________ |JBoss-user mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
