I have similar problems. It seems that the Embedded Catalina version does not read the server.xml file, where I configured some additional contexts. If I call a context defined in the server.xml file I get the error message you posted.
I have also experienced the same exception
as you have described. The embedded version
definitely does not read the config files
Please somebody !!
I've been playing around with this for a few hours and it appears that JBoss doesn't touch the server.xml file. Instead, you must add all this configuration to jboss.jcml like so...
I finally got it all to work - both jsp's and servlets. If you drop a properly configured myapp.war file into the JBoss deploy directory, you can invoke a jsp or servlet. Make sure there is a properly configured web.xml (web-inf/web.xml) file in the war file. Also remember to add "servlet" to the URL when invoking the servlet: http://localhost:8080/myapp/servlet/mypackage.Hello
I did not have to make any changes to jboss.jcml file. I did use Ant for compiling and jar-ing the app but is not required.
Thanks to all who responded.
Oops! You do need to edit the jboss.jcm file as nphelps suggested.
You only have to edit the jboss.jcml file when you want to change the default options (I.E. you want it to run under a port other than 8080 or you want to enable SSL.
I did put an ear file in Jboss's deploy and it works.The Problem is that often Catalina does'nt even recognize the web-app war . I have few application that can run on the previous Jboss with Tomcat servlet engine but when I try to run them on Jboss2.4.4 Catalina start throwing silly exceptions
Is there any explanation to this !
I've tried this configuration within my jboss.jcml file and the port value doesn't work. When I specify another port (8000) or use the default (8080) everything seems to work okay. When I specify port 80 there are a bunch of error messages basically saying that IP address is already in use. Is there something else I need to specify to get it to port 80? Or should I just leave it at the default port?
My JBOSS server will be behind a front end Apache+Tomcat server so the default port won't be a problem. I'd just like to get this working so that I understand better how to configure the servers.
Thanks for any assistance.
Do you have another httpd using port 80 (i.e. apache, iis, etc)? If so, and if it is already up and running, port 80 will not be available for use by another service.
NPHELPS implied that she/he was able to get catalina to read server.xml by adding the mbean to jboss.jcml. Is this true?
The problem of embedded catalina NOT reading server.xml has been around for a while. Is there a fix to this? Have the JBoss developers responded to this issue? Is there a plan to fix this problem?
Had the same problem
"MAPPING configuration error for request URI")
and solved it by adding the folwing row in application.xml in myapp.ear:
You can see the thread which named "JBoss/Tomcat HTTP 500 " on this forum .
I had same problem. But I got it resolved. When I run my home page index.htmlt, the server had the error msg. Late I found a image source url wrong.
Please check if your all url is correct!!!
As the server.xml is not read, how new 'static' context could be added ?
What I want to do is to set up a context not created by jboss during deployment, but mapped to the filesystem to serve a bunch of files.
Anyone know how this could be done ?