Re: The latest Shale/Tiles release results in a 404
On Nov 14, 2006, at 3:24 PM, Dick Starr wrote: Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/starraShale] startup failed due to previous errors These 2 lines concern me. Is that in your catalina.out file? Do you have another log file that contains more detailed error information? It appears something caused the entire web application to be unable to deploy. Is it the Tiles Filter? Greg Thanks for the response. Sorry for my delay in responding back, but I didn't receive either my email or your reply to my email, but I looked on Nabble and found your reply. I am getting the Shale emails again now, however. I am using Netbeans 5.5 with Tomcat 5.5 external. The log information is from my catalina.2006-11-14.log, and no, it sure doesn't say much. You are right, the app does not deploy. If memory serves me right, I have seen the Tiles filter choke and the app fail to deploy before - but I don't remember the exact situation. I reduced my tiles.xml and my layout jsp to the absolute minimum (only a body) but with the same results. My wild guess is that the filter sees something it doesn't like in tiles.xml. However, all this stuff was working before my upgrade. Let me know if you want me to try something. I'll keep plugging on it. Dick
RE: The latest Shale/Tiles release results in a 404
Thanks for the reply. catalina.out contains: Nov 15, 2006 12:01:07 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/java/jdk1.5.0_06/jre/lib/i386/client:/opt/java/jdk1.5.0_06/jre/lib/i386:/opt/java/jdk1.5.0_06/jre/../lib/i386 Nov 15, 2006 12:01:07 PM org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Nov 15, 2006 12:01:08 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1105 ms Nov 15, 2006 12:01:08 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Nov 15, 2006 12:01:08 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Nov 15, 2006 12:01:08 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester). log4j:WARN Please initialize the log4j system properly. Nov 15, 2006 12:01:13 PM org.apache.tiles.listener.TilesListener contextInitialized INFO: Initializing TilesListener Nov 15, 2006 12:01:13 PM org.apache.tiles.listener.TilesListener readFactoryConfig INFO: CONFIG FILES DEFINED IN WEB.XML Nov 15, 2006 12:01:13 PM org.apache.tiles.listener.TilesListener initDefinitionsFactory INFO: initializing definitions factory... 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 Nov 15, 2006 12:01:14 PM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Nov 15, 2006 12:01:15 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Nov 15, 2006 12:01:15 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/39 config=null Nov 15, 2006 12:01:15 PM org.apache.catalina.storeconfig.StoreLoader load INFO: Find registry server-registry.xml at classpath resource Nov 15, 2006 12:01:15 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 7298 ms 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]] I was running Tomcat 5.5.12, but I upgraded to 5.5.17 prior to upgrading Netbeans from 5.0 to 5.5 last week (since Netbeans was tested with 5.5.17). Although the prior version of my app works with 5.5.17 I do see quite a few Google hits on SEVERE: Error filterStart. Should try my earlier version of Tomcat? By the way, I commented out my Tiles listener and used the Tiles Servlet instead. I got the same error. Dick Dick -Original Message- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Wed 11/15/2006 11:40 AM To: user@shale.apache.org Cc: Subject:Re: The latest Shale/Tiles release results in a 404 On 11/15/06, Dick Starr [EMAIL PROTECTED] wrote: The app was deploying (Netbeans automatically removes it when Netbeans shuts down). I am now manually deploying the app to Tomcat. I also removed my own filter. The catalina.out still has the filterStart error: INFO: Starting Servlet Engine: Apache Tomcat/5.5.17 Nov 15, 2006 10:23:56 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled log4j:WARN No appenders could be found for logger ( org.apache.commons.digester.Digester). log4j:WARN Please initialize the log4j system properly. Nov 15, 2006 10:24:01 AM org.apache.tiles.listener.TilesListenercontextInitialized INFO: Initializing TilesListener Nov 15, 2006 10:24:01 AM org.apache.tiles.listener.TilesListenerreadFactoryConfig INFO: CONFIG FILES DEFINED IN WEB.XML Nov 15, 2006 10:24:02 AM org.apache.tiles.listener.TilesListenerinitDefinitionsFactory INFO: initializing definitions factory... Nov 15, 2006 10:24:02 AM
RE: The latest Shale/Tiles release results in a 404
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 suppose that it could be that the latest Shale/Tiles combination has some problem. If anyone has successfully used Shale and Tiles from shale-framework-2006 or later, please send a post identifying the release you are using. Thanks, Dick
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
RE: The latest Shale/Tiles release results in a 404
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: user@shale.apache.org 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
The latest Shale/Tiles release results in a 404
I have been trying to update my Tiles development from release
shale-framework-20061004 (works fine) to shale-framework-2006 (fails). I am
using tiles-core-2.0-r468346-SNAPSHOT.jar, which is included with the Shale
release. I am also using the Tiles 2 FAQ as a guide. I immediately die with a
404 (The requested resource (/starraShale/) is not available.) with the
following Tomcat log entries:
Nov 14, 2006 2:18:03 PM org.apache.tiles.listener.TilesListener
contextInitialized
INFO: Initializing TilesListener
Nov 14, 2006 2:18:03 PM org.apache.tiles.listener.TilesListener
readFactoryConfig
INFO: CONFIG FILES DEFINED IN WEB.XML
Nov 14, 2006 2:18:04 PM org.apache.tiles.listener.TilesListener
initDefinitionsFactory
INFO: initializing definitions factory...
SaInitializer.contextInitialized (Note: This message is from my own listener
that currently does nothing but print his message.)
Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/starraShale] startup failed due to previous errors
I think the problem is in my layout which had entries like
td valign=toptiles:insert flush=false name=body//td,
but now has
td valign=toptiles:attribute flush=false name=body//td
For sure it can't find the first Tile which is accessed via my index.jsp as
follows:
jsp:forward page=systemLogon.faces/
where my tiles.xml has the following entries:
definition name=/systemLogon
extends=/siteMainLayout
put name=body
type=template
value=/jsp/system/logon.jsp/
/definition
definition name=/siteMainLayout
path=/tiles/layouts/starraLayout.jsp
put name=title value=/tiles/common/title.jsp/
put name=header value=/tiles/common/header.jsp/
put name=menuBar value=/tiles/common/menuBar.jsp/
put name=body value=/
put name=footer value=/tiles/common/footer.jsp/
/definition
I have tried every combination I could think of to replace the tiles:insert.
Yes, I tried both tiles:insertTemplate and tiles:insertDefinition (even though
tiles:attribute was the only one that made sense to me). Nothing I have tried
works.
Here is my layout:
%-- starraLayout.jsp
2006-11-14 RJS. New.
--%
%@ include file=/jspf/common/taglibs.jsp %
%@ include file=/jspf/common/messages.jsp %
%-- Layout Tiles
This layout create a html page with header and body tags. It render
a header, left menu, body and footer tile.
@param title String use in page title
@param header: Header tile (jsp url or definition name)
@param menuBar: Menu Bar
@param body: Body
@param footer: Footer
--%
f:view
html
head
link href=h:outputText
value=#{facesContext.externalContext.requestContextPath}/h:outputText
value=#{msg['style.base']}/
rel=stylesheet
type=text/css/
titletiles:attribute flush=false name=title//title
/head
body background=h:outputText
value=#{facesContext.externalContext.requestContextPath}/h:outputText
value=#{msg['img.background.app']}//
table border=0 cellspacing=5 width=100%
tr
td colspan=2tiles:attribute flush=false name=header//td
/tr
tr
td valign=top width=13%
tiles:attribute flush=false name=menuBar/
/td
td valign=top
tiles:attribute flush=false name=body/
/td
/tr
tr
td align=center colspan=2
tiles:attribute flush=false name=footer/
/td
/tr
/table
/body
/html
/f:view
Thanks in advance for your help.
Dick
Re: The latest Shale/Tiles release results in a 404
On Nov 14, 2006, at 3:24 PM, Dick Starr wrote: Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart Nov 14, 2006 2:18:04 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/starraShale] startup failed due to previous errors These 2 lines concern me. Is that in your catalina.out file? Do you have another log file that contains more detailed error information? It appears something caused the entire web application to be unable to deploy. Is it the Tiles Filter? Greg
