OK, this is a tough one to explain but bear with me. I have been contacted by a potential client who is attempting to set up Tomcat 4.1? Dev on an NT server with ONE instance that services multiple partitions. The guy sounds like he knows what hes doing on servers so Im taking him at his word here. The problem is the examples run just fine but anything in any of the partitions throws a 404 error. He says he has the Catalina_Base variable set up along with the Catalina_Home. As I said the examples run fine....my thoughts are he hasnt set up one of the XML files correctly. Im going down there over the weekend to look at this & could use any help putting together a "bug list" before I go instead of floundering around.. The Jakarta instructions, although clear & to the point make me feel somethings missing here as all they discuss is the Catalina_Base when using it across multiple server paritions.... The other thing that bothers me is the fact that the only way to get the Tomcat index.jsp page to come up is by typing the IP:8080 which I know darn well isnt right. Ive used Tomcat on several hosting companies & NEVER had to ad :8080 to my URLs. Any & All help would be appreciated as this could lead to some real work for myself....I do appreciate it.
1. "Dev" == "Development system??? 2. I think by "partition", you mean running multiple Tomcats on the same copy of the OS - something that can be done under Catalina by having a master Tomcat config file plus the config files that define the setups and webapps for each Tomcat instance. BTW, you have to have a unique ip/port address for each Tomcat, no sharing allowed! This isn't some sort of clustering configuration. Any clustering you want from Tomcat is going to be because you or a 3d party wrote something to do the clustering manually - Tomcat isn't like the expensive systems. So typically, you might run a production system under one Tomcat on port 80 and a test system on port 8080. There are few situations where it's advantageous to run multiple Tomcats unless where you are afraid of having one die and take multiple webapps down, since each Tomcat carries the overhead of a separate Java VM.
Customer surveys are for companies who didn't pay proper attention to begin with.