The logging.properties files are clones of the example at the bottom of the Tomcat 5.5 docs logging.htm page, with the exception of the ..FileHandler.prefix being changed. They reside as below for all three servers (where ServerRootDir is different for each server):
F:/InetPub/ServerRootDir/WEB-INF/classes/logging.properties The realm for the server in question is as below: <Realm className="org.apache.catalina.realm.JDBCRealm" connectionName="name" connectionPassword="pw" connectionURL="jdbc:mysql://mysqldev/ext_principals" digest="MD5" driverName="com.mysql.jdbc.Driver" roleNameCol="role" userCredCol="password" userNameCol="username" userRoleTable="user_roles" userTable="users" /> Thanks Boris, I appreciate the help. Sincerely, Craig > -----Original Message----- > From: Boris Unckel [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 26, 2006 10:45 AM > To: Tomcat Users List > Subject: Re: tomcat 5.5.15 - does JULI required a host tag defined realm? > > SNIP > > No, thats more a problem of the classloader. The logging config is per > Context Classloader. So you can place a logging properties at any place in > the classloader hierarchy. > It seems that you have same the logging.properties in your webapp, but > just > changed the entry of the realm. > Does the entry of the realm change the classloader (hierarchy) behaviour? > > Please send all your logging.properties and a short comment where they > placed. > > Regards > Boris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
