You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Simone Chiaretta <si...@logicapiu.it> on 2003/02/20 11:40:44 UTC

Server.xml messed up by /admin web apps

Hello All,
I've just upgraded from tomcat 4.0.4 to 4.1.18 and put it on a test server
to test and see if it works with my enviroment.

The first thing I've done was to replicate the production server structure
to my dev server, so I added with the /admin web interface some Hosts and
one "blank" Context for each Host.
Then I applyed the changes and... booom  no Host started toi run...

the jsp pages in the root dir did not excute and I see the code instead of
the execution, while the pages inside the subdirs didn't compile and give a
Jasper compilation error... the page won't compile but error is generated in
the some jasper.* class

So I made a test, rolled back the server.xml to the default one and addedd
Hosts and Context manually to the file (old-style :-))
and now everything works...

Does anybody have ever experienced the problem?

Simone


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org