We've set up a single software installation of Tomcat, but have different
developers running their own Tomcat process by supplying their own
server.xml file with separate directories and ports lists for each
developer.
This works mostly fine, except for the admin settings. Just doing the above
leads to a situation where the web server complains about not being able to
write the tomcat-apache.html file on startup:
Failed to generate automatic apache configuration
java.io.FileNotFoundException: /opt/jakarta-tomcat/conf/tomcat-apache.conf
(Permission denied)
Also, when I use /admin (contextAdmin) to look at the contexts known to the
web server, I notice that whereas the various contexts listed in my
server.xml file all appear with references to my local work area (i.e. my
use of Tomcat), the /admin context refers to the central installation
directory (which I deliberately can't write to).
My next step was to add a /admin context to my server.xml file pointing at
my local area. This showed up correctly on the contextAdmin screen, but the
server still complains on the way up about not being able to generate the
automatic apache configuration (message as above).
What am I doing wrong?
********************************************************************
This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorised to
retain, read, copy or disseminate this message or any part of it.
********************************************************************
