On Nov 15, 2006, at 12:31 PM, Dick Starr wrote:
catalina.out contains:
[snip]
Nov 15, 2006 12:01:13 PM org.apache.catalina.core.StandardContext
start
SEVERE: Error filterStart
Nov 15, 2006 12:01:13 PM org.apache.catalina.core.StandardContext
start
SEVERE: Context [/starraShale] startup failed due to previous errors
[snip]
and localhost.2006-11-15.log contains:
Nov 15, 2006 12:01:14 PM
org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Nov 15, 2006 12:01:14 PM
org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Nov 15, 2006 12:01:14 PM
org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Nov 15, 2006 12:01:14 PM
org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Nov 15, 2006 12:01:14 PM
org.apache.catalina.core.ApplicationContext log
INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
[org.apache.webapp.balancer.RuleChain:
[org.apache.webapp.balancer.rules.URLStringMatchRule: Target
string: News / Redirect URL: http://www.cnn.com],
[org.apache.webapp.balancer.rules.RequestParameterRule: Target
param name: paramName / Target param value: paramValue / Redirect
URL: http://www.yahoo.com],
[org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect
URL: http://jakarta.apache.org]]
There's a couple of things we need to figure out just to determine if
the problem is even Tiles-related or Shale-related.
Are you running Tomcat from Netbeans? I use Netbeans 5.0 and point
it to an external Tomcat 5.5.17. When I run the app I have 2 extra
tabs in my output window. One is the catalina.out and catalina.$
{date}.log files and it's labeled "External Tomcat 5.5". The other
one is the localhost-${date}.log file and it's labeled "External
Tomcat 5.5 Log". When an application fails to deploy I sometimes
have to check both of them. Often the error will appear only in the
localhost*.log file. It kinda looks like you're not getting anything
useful in either one.
If the Tiles Filter is blowing up it should be throwing an exception
and printing that out to the log. Can you try commenting out the
Tiles Filter in your web.xml and see if the app deploys? The lack of
a filter should not keep the app from deploying. In fact I don't
think the filter actually does anything except allow you to reload
tiles defs that have changed.
Do you have any other filters in your app? If so, try commenting
them out one by one and see if the error goes away or changes.
The problem is definitely related to a filter failing to initialize.
Now the question is which one and what's going wrong? Truthfully,
I'm really surprised your localhost log is not helping more.
Ah, I just found one more thing:
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.
Can you add a log4j.properties to your WEB-INF/classes and see if you
get more spew in the localhost.log file?
Greg
