Scott/all: I believe that something is amiss with my Tomcat4 server.xml configuration.
According to the catalina.out startup log files, CatalinaPAM is forced into a file system mode because it cannot ping the manager webapp. Afterward, It does not appear to attempt to reach the manager webapp, (as the error messages at startup would indicate/predict). Everything seems to be OK because the Tomcat deployer is picking up the portlet webapps in my case... but what is the point then of the manager webapp being there? Am I missing something? I am not sure what I should change to get the manager webapp into the act. It is in the same service/server container as jetspeed and will not be available at startup because Tomcat has not enabled services on the HTTP port it is trying to reach. Should the manager app be in the same or a different server.xml Engine or Service as jetspeed? Just throwing it out there. I do not see anything significantly different in my configuration when compared with etc/server.xml in the J2 cvs repositiory. On a related topic, I seem to recall David Taylor and Ate discussing the Host autoDeploy attribute... should it be set to "false" so the jetspeed and Tomcat deployers are not fighting over the portlet webapps? Sorry guys for the lame questions, I just want to get into an officially correct configuration before I debug further! Randy
