Derek, Rich was instructing you to turn on security debug in your Tomcat startup options so that any security violations are clearly indicated in your logs. To do that, modify the startup file for Tomcat. For example, I use the following in my starttomcat.bat file so that security.debug is set to access, failure:
start %JAVA_HOME%\bin\java.exe -Djava.io.tmpdir=%CATALINA_HOME%\work\temp -Dcatalina.home=%CATALINA_HOME% -Djava.security.debug=access,failure -Djava.security.manager -Djava.security.policy==%CATALINA_HOME%\conf\catalina.policy org.apache.catalina.startup.Bootstrap start -config %CATALINA_HOME%\conf\server.xml > %CATALINA_HOME%\logs\jvmstderr.log Review your startup file and make the appropriate change to the -Djava.security.debug option. After you do this, any security violations will be clearly indicated in your logs, such as logs/localhost_log.2002-04-24.txt. You will see the domain that failed and it should be simple for you to copy and paste the needed permission into your catalina.policy file. If you're uncertain what to put in your policy, send the offending stack trace to the list and I'm sure someone will help. Regards, Garrel Renick [EMAIL PROTECTED] -----Original Message----- From: Derek Doerr [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 6:48 PM To: Tag Libraries Users List Subject: Re: Mailer Taglib SecurityException Rich, I'm running Tomcat 4.0.2. I suspect that the security changes that you reference, below, should be made to the catalina.policy file. Do you know what the change would be? Also, do you know where, in the server.xml file I would turn on security debugging? Thanks! - Derek -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
