I sure appreciate your help Greg. I have tried all of your suggestions, but no results so far. My app was deploying earlier when I was deploying it manually by copying the jar over but fails now since I re-installed Tomcat 5.5.17 - probably a permissions problem. I commented out my Tiles Listener and CommonChains listener. I have run out of time for today, but I will dig back into it tomorrow morning.
Could you please take a look at my log4j? # log4j.properties # 2006-11-15 RJS. New, from "The complete Manual log4j", page 61. # Create two appenders: C1 (console) & F1 (file). # Output internal log4j debugging messages to the console. log4j.debug=true # Set root logger level to DEBUG and its only appender to C1. log4j.rootLogger=DEBUG, C1 # C1 = console. log4j.appender.C1=org.apache.log4j.ConsoleAppender # In production, set C1.Threshold to INFO (or nix it completely). log4j.appender.C1.Threshold=INFO log4j.appender.C1.layout=org.apache.log4j.PatternLayout log4j.appender.C1.layout.ConversionPattern=%d - %p %c - %m%n # F1 = RollingFileAppender. log4j.appender.F1=org.apache.log4j.RollingFileAppender # Put "starra.log" in the local dir (correct for netbeans). log4j.appender.F1.File=/home/dick/starraShale.log log4j.appender.F1.MaxFileSize=200KB # Keep one backup file of F1. log4j.appender.F1.MaxBackupIndex=1 log4j.appender.F1.layout=org.apache.log4j.PatternLayout log4j.appender.F1.layout.ConversionPattern=%d - %p %c - %m%n # test log4j.logger.com.ibatis=DEBUG, F1 log4j.logger.java.sql=DEBUG, F1 # Spring Framework log4j.logger.org.springframework=DEBUG, F1 # Starr Accounting. log4j.logger.com.starrcs=TRACE, F1 log4j.logger.org.apache.commons.digester=TRACE, F1 Thanks, Dick ---- -----Original Message----- From: Greg Reddin [mailto:[EMAIL PROTECTED] Sent: Wed 11/15/2006 2:40 PM To: [email protected] Cc: Subject: Re: The latest Shale/Tiles release results in a 404 On Nov 15, 2006, at 2:26 PM, Dick Starr wrote: > My problems don't seem to be Tomcat related. I have tried my earlier > Tomcat (5.5.12) as well as the latest 5.5 Tomcat (5.5.20). I don't think it's a Tomcat problem either. I think you have a filter failing, but we're not seeing why. If the filter is logging information, but you don't have log4j configured correctly, that may be why we don't see the logs. I've had that exact problem before and it behaved differently across different versions of Tomcat. My suspicion is that it is related to TilesFilter, but I can't help if I don't know what the exception is :-) When I added a simple log4j.properties file to my web app I saw a lot more helpful information. Greg
