Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification.
The "HowTo" page has been changed by KonstantinKolinko: http://wiki.apache.org/tomcat/HowTo?action=diff&rev1=106&rev2=107 Comment: Remove tip that suggests editing setclasspath.sh. I think it is just wrong. b) Edit the file ''catalina.properties'' under {{{$CATALINA_BASE/conf}}}; there is a property called ''common.loader'' to which you can add additional paths to find JARs or classes for the common classloader. - == How do I get Tomcat to start when it says it can't find the file 'setclasspath.sh'? == - If Tomcat was working fine the first few times after installation but suddenly refuses to start up and gives the following error message: - - {{{ - $ ./startup.sh - Cannot find /path/to/tomcat/bin/setclasspath.sh - This file is needed to run this program - }}} - Then all you need to do is to include the complete paths for the BASEDIR and CATALINA_HOME variables in the files setclasspath.sh and catalina.sh respectively. - - This should be done even if CATALINA_HOME has been defined and exported previously on the command line and/or in /etc/profile as well. Moreover, this error message persists even though the file setclasspath.sh is present in Tomcat's bin directory. - - {{{ - $ echo "BASEDIR=/path/to/tomcat" >> setclasspath.sh - $ echo "CATALINA_HOME=/path/to/tomcat" >> catalina.sh - }}} == How do I authenticate Manager access via JNDI to Active Directory for multiple Tomcat instances? == ADS insists that the CN of every group be unique, but the Manager app. always uses the group CN=manager. The default can be changed, but it's hard to find and you have to do it over every time you upgrade. Instead, pick an attribute other than the common name -- for example, "description" -- that doesn't have to be unique, name it as the `RoleName` attribute of the `Realm` (in server.xml, which you'll be editing anyway), and set that attribute to "manager" in each group you create. Create an OU for each Tomcat instance's groups and give that OU's DN as the `RoleBase` in that instance's server.xml. Create a uniquely-named group in each instance's OU with the chosen attribute ("description" for example) set to "manager". --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
