Tomcat 4.x originally came with just mod_webapp as the connector, which doesn't require these extra files that mod_jk does. Integration of mod_jk support with Tomcat 4.x is still on going. Since Tomcat 3.x is quite different from Tomcat 4.x (compare server.xml files for example), is means that some of what you find in the Tomcat 3.3 documentation isn't going to apply to Tomcat 4.x. The "jkconf" option is a good example. This is a feature that applies only to Tomcat 3.3. None of the Tomcat 4.x releases does auto-config generation (mod_webapp didn't need it). I believe the next releases of Tomcat 4.x will contain some support for this. For the time being you have to create them manually, or if you feel like investing in the disk space, install a version Tomcat 3.3 to help generate them.
Cheers, Larry > -----Original Message----- > From: Scott Merritt [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 17, 2001 6:50 PM > To: 'Tomcat Users List' > Subject: jkconf? Does it work in 4.0.1? Where's workers.properties? > > > Hmm... My next question is, how come I can't find a > workers.properties file? > > I'm using Tomcat 4.0.1 and trying to get it to autgen the > config files... > None of these generate anything: > ./startup.sh jkconf > ./catalina.sh jkconf > > Okay... So I figured I'd do it manually, but I don't see any > workers.properties file to follow the "simple" example in the > 3.3 mod_jk > docs > (http://jakarta.apache.org/tomcat/tomcat-3.3-doc/mod_jk-howto.html) > > Hmm... Now what? Confused. Does Tomcat 4 not do this conf writing > anymore? > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
