9 Replies Latest reply on Mar 12, 2002 4:39 PM by troydoux

    JBoss 2.4.4 and Tomcat 4.0.1

    westam

      I just downloaded and installed this.
      The readme says to enable tomcat uncomment a pragma in jboss.conf but it is not there in the default configuration but there is a pragma in the jboss.jcml (btw is this job control markup language? This brings back a few memories from MFT, MVT and MVS days).
      When I enable this I get exceptions trying to load the tomcat class. I presume I need some jars in the classpath. I purchased the install and admin doc but it does not seem to cover this.

      Martin West

        • 1. Re: JBoss 2.4.4 and Tomcat 4.0.1
          juergenheidak

          1. Give more information about the exception (stacktrace).

          2. At least the tools.jar located somewhere under the installation directory of your jdk needs to be copied to jboss-dir/lib/ext to enable compiling of servlets.

          • 2. Re: JBoss 2.4.4 and Tomcat 4.0.1
            westam

            I dont get as far as compiling servlets, first part of the log ....
            [martin@rh1 bin]$ sh run.sh
            JBOSS_CLASSPATH=:run.jar:../lib/crimson.jar
            jboss.home = /opt/JBoss-2.4.4_Tomcat-4.0.1/jboss
            Using JAAS LoginConfig: file:/opt/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/default/auth.conf
            JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
            JBoss version: 2.4.4.2001-12-29 02:04:40 PST
            Using configuration "default"
            [INFO,root] Started Log4jService, config=file:/opt/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/default/log4j.properties
            [INFO,Info] Java version: 1.3.1_01,Sun Microsystems Inc.
            [INFO,Info] Java VM: Java HotSpot(TM) Server VM 1.3.1_01,Sun Microsystems Inc.
            [INFO,Info] System: Linux 2.4.7-10,i386
            [INFO,Shutdown] Shutdown hook added
            [ERROR,ConfigurationService] Could not create MBean DefaultDomain:service=EmbeddedTomcat(org.jboss.tomcat.EmbeddedTomcatServiceSX)
            java.lang.ClassNotFoundException: org.jboss.tomcat.EmbeddedTomcatServiceSX
            at javax.management.loading.MLet.findClass(MLet.java:800)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
            at com.sun.management.jmx.MBeanServerImpl.findClass(MBeanServerImpl.java:2466)
            at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:751)
            Thanks for the help
            Martin West

            • 3. Re: JBoss 2.4.4 and Tomcat 4.0.1
              jafarnham

              I think this is the same issue I've been trying to work out today. In case this is still causing you problems, here's what I did to (hopefully) eliminate similar errors that I was seeing while started up with embedded tomcat. I haven't done much testing with tomcat yet, but at least I'm not getting the startup errors.

              My problem seemed to be that the structure of the tomcat jar file was different than expected by jboss.jcml. The jboss.jcml that came with my JBoss 2.4.4/Tomcat 4.0.1 distribution tried to start the tomcat service using the same class name you're showing--org.jboss.tomcat.EmbeddedTomcatServiceSX.

              I didn't have this class in any of the jar files that came with my distribution. However, my catalina-service.jar had a class with this name at org.jboss.web.catalina.EmbeddedTomcatServiceSX. I got rid of this error by changing the embedded tomcat line in jboss.jcml to:



              I also had a similar error when starting the JBossMQ service, which had a similar resolution.

              Hope this helps,
              Jessica

              • 4. Re: JBoss 2.4.4 and Tomcat 4.0.1
                shogun1234

                i have similar problem like first post, but it states "null pointer" occurred! how to solve it?
                thanks in advice,

                [ERROR,EmbeddedCatalinaServiceSX] HttpProcessor[8080][4] process.invoke
                java.lang.NullPointerException
                at org.apache.catalina.valves.ErrorDispatcherValve.status(ErrorDispatche
                rValve.java:280)
                at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatche
                rValve.java:180)
                at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
                .java:564)
                at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
                ava:170)
                at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
                .java:564)
                at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
                a:472)
                at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

                at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
                ve.java:163)
                at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline
                .java:566)
                at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
                a:472)
                at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)

                at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcesso
                r.java:1011)
                at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.ja
                va:1106)
                at java.lang.Thread.run(Thread.java:484)

                • 5. Re: JBoss 2.4.4 and Tomcat 4.0.1
                  mao2192

                  You could just deploy a dummy app at the root context ( / ). when i downloaded JBoss-2.4.3_Tomcat-4.0.1, the first thing i did was wipe the deploy directory.. toss something in there that references / in the application.xml and you will be all set...

                  This solution is found in many places in the forums.

                  • 6. Re: JBoss 2.4.4 and Tomcat 4.0.1
                    amowers

                    I am seeing this same error.

                    What is the work around for this? Does it have anything to do with the fact I am using jdk1.4 on my windows2000 installation. (please no snide remarks about windows :-) )

                    • 7. Re: JBoss 2.4.4 and Tomcat 4.0.1
                      rgjawanda

                      I think I got almost everything working becuase I got all the examples to work. The only one that doesn't is the interest.ear which is the test inside the web browser.

                      I had to do some real fiddling with the installation.
                      I copied the tomcat jakarta-tomcat-4.0.3-LE-jdk14 version into the JBoss-2.4
                      .4_Tomcat-4.0.1/catalina directory
                      replacing the 4.0.1 version with 4.0.3 version.

                      I think the examples are wrong with the interest.ear file.
                      I believe they missed an xml file but I am no expert here.
                      I hope someone can help.



                      Here is my error (I took this part out of the junk below)
                      ---------
                      org.jboss.deployment.J2eeDeploymentException: application contains war files but no web container available
                      at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:496)
                      at

                      ---------------

                      Hmmmm...






                      [INFO,ContainerFactory] Deploying:file:/usr/local/JBoss-2.4.4/tmp/deploy/Default/interest.ear
                      [INFO,ContainerFactory] Deploying Interest
                      [INFO,Interest] Initializing
                      [INFO,Interest] Initialized
                      [INFO,Interest] Starting
                      [INFO,Interest] Started
                      [INFO,ContainerFactory] Deployed application: file:/usr/local/JBoss-2.4.4/tmp/deploy/Default/interest.ear
                      [ERROR,J2eeDeployer] Unable to stop module interest.war: DefaultDomain:service=EmbeddedTomcat
                      [INFO,J2eeDeployer] Stopping module interest.ear
                      [INFO,ContainerFactory] Undeploying:file:/usr/local/JBoss-2.4.4/tmp/deploy/Default/interest.ear
                      [INFO,Interest] Stopping
                      [INFO,Interest] Stopped
                      [INFO,Interest] Destroying
                      [INFO,Interest] Destroyed
                      [INFO,Interest] Destroying
                      [INFO,Interest] Destroyed
                      [INFO,ContainerFactory] Undeployed application: file:/usr/local/JBoss-2.4.4/tmp/deploy/Default/interest.ear
                      [ERROR,J2eeDeployer] unable to stop application interest.ear: org.jboss.deployment.J2eeDeploymentException: Error(s) on stopping application interest.ear:
                      Unable to stop module interest.war: fatal error while calling :service=EmbeddedTomcat: DefaultDomain:service=EmbeddedTomcat/n
                      [INFO,J2eeDeployer] Destroying application interest.ear
                      [ERROR,AutoDeployer] DeploymentInfo failed:file:/usr/local/JBoss-2.4.4/deploy/interest.ear
                      org.jboss.deployment.J2eeDeploymentException: application contains war files but no web container available
                      at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:496)
                      at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:459)
                      at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:190)
                      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:324)
                      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
                      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
                      at org.jboss.deployment.AutoDeployer.deploy(AutoDeployer.java:395)
                      at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:233)
                      at org.jboss.deployment.AutoDeployer.startService(AutoDeployer.java:371)





                      • 8. Re: JBoss 2.4.4 and Tomcat 4.0.1
                        xj02

                        I also got the problems to install JBoss 2.4.4 and Tomcat 4.0.1.
                        I run run_with_catalina.bat and got errors like:
                        ./run_with_catalina.bat: @echo: command not found
                        ./run_with_catalina.bat: fg: no job control
                        ./run_with_catalina.bat: .run.bat: command not found
                        : command not found.bat:
                        I really have no idea about that, anyone could help? Thanks!

                        • 9. Re: JBoss 2.4.4 and Tomcat 4.0.1
                          troydoux

                          xj02, it looks like you're running DOS batch file on a Unix system. Try running run_with_catalina.sh instead