I've got the same problem. I had kicked off Tomcat before i started the jboss server and came up with the same error.
see the following note during jboss startup:
[INFO,J2eeDeployer] No web container found - only EJB deployment available...
and then the error below:
[ERROR,J2eeDeployer] 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
[INFO,J2eeDeployer] Destroying application tomcat-test.ear
[ERROR,AutoDeployer] DeploymentInfo failed:file:/home/marconi/users/jec/java/JBoss/JBoss-2.4.4_Tomcat-4.0.1/jboss/deploy/tomcat-test.ear
org.jboss.deployment.J2eeDeploymentException: application contains war files but no web container available
Well, I'll assume its Jboss + Tomcat not Jboss + Apache or Jboss + Jetty.
I could be wrong but I think you are trying to start the two packages seperately so jboss is not finding Tomcat. Try going into the jboss/bin directory and doing run_with_catalina.sh or on a doze box run_with_catalina.bat.
Just a thought.
That was too easy. thanks!
ps.. yes jboss+tomcat
I got it to start up without errors, but can't
figure out how to access the tomcat-test app. Every
URL I can think to try just displays
HTTP Status 500 - No Context configured to process this request
I figured it out. I'm used to standalone Tomcat
behavoiur, where the context comes from the .war file's
name. I found the /jboss context-name in the
application.xml file in the .ear