6 Replies Latest reply on Jun 7, 2005 4:13 AM by Cat

    Can't run Jetty on 4.02

    Gil Katz Newbie

      i Downloaded and compile jetty 5.1.4rc0 with Jboss 4.0.2.
      i changed all necessary files and when i run Jboss it seems allright
      but when i try to access to jmx-console or web-console or what ever other application i get

      java.lang.NoClassDefFoundError: org/apache/catalina/core/StandardWrapperFacade
      at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java)
      at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:832)
      at org.mortbay.jetty.servlet.jsr77.Jsr77Filter.doFilter(Jsr77Filter.java:77)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
      at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
      at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:275)
      at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:169)
      at org.mortbay.jetty.servlet.Default.handleGet(Default.java:312)
      at org.mortbay.jetty.servlet.Default.service(Default.java:232)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:832)
      at org.mortbay.jetty.servlet.jsr77.Jsr77Filter.doFilter(Jsr77Filter.java:77)
      at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
      at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
      at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
      at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:623)
      at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
      at org.mortbay.http.HttpServer.service(HttpServer.java:954)
      at org.jboss.jetty.Jetty.service(Jetty.java:456)
      at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
      at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
      at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
      at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
      at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
      at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

        • 1. Re: Can't run Jetty on 4.02
          Amit Bhayani Newbie

          It is really bad idea to use Jetty with JBos4.0.2.
          4.0.2 ships with tomcat 5.5 and is recommended.

          Amit.

          • 2. Re: Can't run Jetty on 4.02
            Cat Newbie

             

            "amit.bhayani@jboss.com" wrote:
            It is really bad idea to use Jetty with JBos4.0.2.
            4.0.2 ships with tomcat 5.5 and is recommended.

            Amit.

            Would you please explain why Tomcat is prefer for JBoss? Can you persuade me to use Tom instead Jetty? Should confess, I have some experience with Tom and prefer don't use it at all, but may be you know something that can share. I'll appreciate for any comment on this. Thanx.

            • 3. Re: Can't run Jetty on 4.02
              Sacha Labourey Master

              You can use whatever you like, it is really up to you.

              Fact is that we provide an integrated Tomcat version (meaning it integrates with clustering, deployment, security, etc.) and we make sure it is very well working with JBoss AS for each release we do. As we don't do it for Jetty (or any other servlet container), it is going to be your responsibility to make sure it works.

              Now an interesting question would be: why do you prefer not to use Tomcat at all?

              cheers,


              sacha

              • 4. Re: Can't run Jetty on 4.02
                Cat Newbie

                Thanx a lot for responce. On first, must make an excuses for my english, it is very poor. I just trying to satisfy Your curiosity. :)

                "sacha.labourey@jboss.com" wrote:
                You can use whatever you like, it is really up to you.
                Fact is that we provide an integrated Tomcat version (meaning it integrates with clustering, deployment, security, etc.) and we make sure it is very well working with JBoss AS for each release we do. As we don't do it for Jetty (or any other servlet container), it is going to be your responsibility to make sure it works.

                Now an interesting question would be: why do you prefer not to use Tomcat at all?

                cheers,
                sacha


                Sounds good... :) But I really confused why JBoss prefers Tom. So, why I ahead the Tom? Because it:
                a.) Has unexpected behaviour from release to release. Btw, it has 3 deployment scheme (4.x, 5.0.x, 5.5.x) at that 5.5.x and 4.x is not compliant at all. Moreover seems like deployment scheme is still under design, I think (why context.xml is unpacket to /conf?). And, can You see any Maven's plugin (should be addmitted I prefer it) that is working with each Tom? Please, let me know, if there is any. :) I think it has so knotty deployment that this task never be resolved?
                b.) Its configuration is just a big joke, seems like Jakarta provides samples how the Tom can be configured (btw, try to configure the DataSource in 4.x and in 5.x, You'll be just a wonder) within each release.
                c.) It is very huge as for just a Web container. The Jetty more small and transparent as for me. Btw, try to add the MBean to Tom, even with simplest lifecycle. Should note this task can spend more time that You can expect. :)
                I can continue, but think there is more guys that can provide more arguments by more readable english.
                P.S. What security You mean? JAAS? Web? Excuse me, I can't imaginate how JBoss can be depend from Tom's in this scope... Btw, Tom has the default JDBC Realm that is not always can be customized, since not always User model can be applied to suggested. I think it is poor design where You shouldn't provide just a simple SQL to fetch principal credentials.
                P.S.S. About clustering. Should note that I haven't any experience in clustering , therefore can't talk about this. However, seems like it is not only Tom's feature. I think that there only HTTP session replication can be resolved... Do You agreed?
                Thanx.

                • 5. Re: Can't run Jetty on 4.02
                  Sacha Labourey Master

                  Well, pretty much everything you describe in your e-mail are features that are handled by JBOSS and not by Apache Tomcat directly: JMX, clustering, deployment, security, datasources, etc. so you'd better deploy them as JBOSS services and simply rely on the servlet engine for WAR (or EAR) files. And even in that case, the deployment process is handled by JBoss, not Apache Tomcat.

                  We provide Apache Tomcat by default because we contribute to this project (and hence are able to provide quality support for it).

                  cheers,

                  sacha

                  • 6. Re: Can't run Jetty on 4.02
                    Cat Newbie

                     

                    "sacha.labourey@jboss.com" wrote:
                    Well, pretty much everything you describe in your e-mail are features that are handled by JBOSS and not by Apache Tomcat directly: JMX, clustering, deployment, security, datasources, etc. so you'd better deploy them as JBOSS services and simply rely on the servlet engine for WAR (or EAR) files. And even in that case, the deployment process is handled by JBoss, not Apache Tomcat.

                    We provide Apache Tomcat by default because we contribute to this project (and hence are able to provide quality support for it).

                    cheers,

                    sacha


                    Sure. Therefore I just loves JBoss. :) However as I can see in last time JBoss has more tight couples with Tomcat (seems like somewhere JBoss back-end has dependency from Catalina (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=63712): java.lang.NoClassDefFoundError: org/apache/catalina/core/StandardWrapperFacade)...
                    JBoss always was the "best of best" when provide the both Tom and Jetty. Hopes it will stay same always... ;)

                    Thanx a lot,
                    Good luck.