1 Reply Latest reply on Sep 4, 2001 2:12 PM by toby cabot

    Basic help with tomcat part of JBoss-2.4.0_Tomcat-3.2.3?

    David M. Karr Newbie

      I've been developing a test EJB app with JBoss-2.2.2. I installed JBoss-2.4.0_Tomcat-3.2.3, and after some configuration work, I was able to deploy my EJB app and run all of my tests. So far so good.

      Now I want to do some basic testing of the web server part. I noticed the default web server port appears to be 8083. When I go to "localhost:8083", I go to a page listing the $JBOSS_HOME/conf directory. That appears to be a
      milestone.

      Now, I'd like to turn on Tomcat logging so I can see things that are happening. I don't see any place that Tomcat logs would go. I tried creating a simple "stuff.jsp" (just containing a plain "hello, world" html file) in the "webapps" directory and restarting, but when I try to go to "http://localhost:8083/stuff.jsp", I get a "Document contains no data" error.

      I'd appreciate any help I can get to move forward from this.

      Paging through the "server.log" file, I noticed several interesting things, some of which are probably known, and not a problem. I would attach the file here, but that doesn't seem to be very practical in these web forums.

      I noticed the following lines:

      [Configuration] Detected JMX Bug: Server reports attribute 'ConnectionManagerFactoryName' is not writeable for MBean 'JCA:name=MinervaDS,service=ConnectionFactoryLoader'

      [Configuration] Detected JMX Bug: Server reports attribute 'Backlog' is not writeable for MBean 'DefaultDomain:service=Naming'

      [Configuration] Detected JMX Bug: Server reports attribute 'ConnectionManagerFactoryName' is not writeable for MBean 'JCA:name=JmsXA,service=ConnectionFactoryLoader'


      Is this a problem?

      Trivial, but there's a typo in the following message (JDNI):

      [Container factory] Binding securityDomain: java:/jaas/sgs to JDNI ENC as: security/security-domain


      Apparently there is an application that gets auto-deployed, called "tomcat-test", and then apparently it tries to undeploy it. I see the following:

      [Container factory] Undeployed application: file:/C:/JBoss-2.4.0_Tomcat-3.2.3/jboss/tmp/deploy/Default/tomcat-test.ear

      [J2EE Deployer Default] unable to stop application tomcat-test.ear: org.jboss.deployment.J2eeDeploymentException: Error(s) on stopping application tomcat-test.ear:
      Unable to stop module tomcat-test.war: fatal error while calling :service=EmbeddedTomcat: DefaultDomain:service=EmbeddedTomcat/n

      [J2EE Deployer Default] Destroying application tomcat-test.ear

      [AutoDeployer] Deployment failed:file:/C:/JBoss-2.4.0_Tomcat-3.2.3/jboss/deploy/tomcat-test.ear

      [AutoDeployer] org.jboss.deployment.J2eeDeploymentException: application contains war files but no web container available

      [AutoDeployer] at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:493)