7 Replies Latest reply on Jan 23, 2004 7:30 AM by kryptontri

    Jetty vs Apache/Tomcat

    balsini

       

      "balsini" wrote:
      "balsini" wrote:
      "balsini" wrote:
      "balsini" wrote:
      Positive and Negative points, Jetty/Jboss 3.0 vs Apache/TomCat/Jboss 3.0 ?


        • 1. Re: Jetty vs Apache/Tomcat
          sairam_70

           

          "sairam_70" wrote:
          "sairam_70" wrote:
          "sairam_70" wrote:
          "sairam_70" wrote:
          > Positive and Negative points, Jetty/Jboss 3.0 vs
          > Apache/TomCat/Jboss 3.0 ?

          Dear balsini ,

          1. You cannot just compare the Jetty Vs Apache Tomcat for Web Containter selection . Because both are for different dimensions of deployment .

          Balaji Venkatraman
          Lead Architect



          • 2. Re: Jetty vs Apache/Tomcat
            johan31be

             

            "johan31be" wrote:
            "johan31be" wrote:
            "johan31be" wrote:
            "johan31be" wrote:
            hello,

            In the past i did a peformance test between jetty and tomcat. Same web application tested with jboss-jetty was faster then jboss-tomcat, but that was a year ago

            Greetings Johan


            • 3. Re: Jetty vs Apache/Tomcat
              trajano

               

              "trajano" wrote:
              "trajano" wrote:
              "trajano" wrote:
              "trajano" wrote:
              One positive note is that Jetty is more "space in the path" friendly that Tomcat. I run JBoss in C:\Program Files myself.


              • 4. Re: Jetty vs Apache/Tomcat
                cavedan

                 

                "cavedan" wrote:
                "cavedan" wrote:
                "cavedan" wrote:
                "cavedan" wrote:
                Some additional info comparing a variety of servlet containers: http://webperformanceinc.com/library/ServletReport/


                • 5. Re: Jetty vs Apache/Tomcat
                  mlassau

                   

                  "mlassau" wrote:
                  "mlassau" wrote:
                  "mlassau" wrote:
                  "mlassau" wrote:
                  A huge advantage in our particular case was that Jetty can serve static http pages as well as Servlets.
                  In order to do this with Tomcat, you need to add yet another layer to your architecture (eg Apache-Tomcat-JBoss)
                  There is some work involved in attaching Apache to Tomcat with mod_jk.

                  Also I found it impossible to find a compiled Apache binary for win32 with BOTH mod_jk and SSL (support for these must be compiled in). This was over a year ago, so this may have changed by now.


                  • 6. Re: Jetty vs Apache/Tomcat
                    hercule

                     

                    "hercule" wrote:
                    "hercule" wrote:
                    "hercule" wrote:

                    A huge advantage in our particular case was that Jetty can serve static http pages as well as Servlets.
                    In order to do this with Tomcat, you need to add yet another layer to your architecture (eg Apache-Tomcat-JBoss)
                    There is some work involved in attaching Apache to Tomcat with mod_jk.

                    Also I found it impossible to find a compiled Apache binary for win32 with BOTH mod_jk and SSL (support for these must be compiled in). This was over a year ago, so this may have changed by now.


                    Hi,
                    I'm not ok with this....Tomcat can serve gifs or HTML pages as well...
                    It won't be as fast & reliable than apache but for dynamic most applications it's a sufficient solution...
                    Getting a working mod_jk is the eternal problem, you're right :)


                    • 7. Re: Jetty vs Apache/Tomcat
                      kryptontri

                       

                      "kryptontri" wrote:
                      Jetty and Tomcat can BOTH serve static content e.g html, images etc. .. with tomcat 5, if you look around, there have been a number of performance increases, ie, we are now moving to a stack where it is possible in some scenarious/architectures to do away with a native http server (from a speed/throughput point of view).