You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Hans Hedung <fr...@hotmail.com> on 2007/10/25 16:14:53 UTC

struts-tiles migration issues










Hello,im having difficulties migrating my 1.1 struts app from websphere 5.1 to websphere 6.1.in short, the same difficulties as this post: http://issues.apache.org/struts/browse/TILES-201 Im using RAD 7.0.0.4.Everything works fine on WAS 5.1. Migrating to WAS 6.1 works fine, for starters, aswell, and I dont get any error deploying my webapp on the server but when I try to access my start page I get the following error_log:  ------Start of DE processing------ = [2007-10-25 09:33:09:590 CEST] , key = java.io.FileNotFoundException com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest 573Exception = java.io.FileNotFoundExceptionSource = com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequestprobeid = 573Stack Dump = java.io.FileNotFoundException: /.welcomeat com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:362)at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:274)at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:320)at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463)at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:518)at org.apache.struts.taglib.logic.ForwardTag.doEndTag(ForwardTag.java:170)at com.ibm._jsp._index._jspx_meth_logic_forward_0(_index.java:100)at com.ibm._jsp._index._jspService(_index.java:74)at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:85)at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966)at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463)at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:115)at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:168)at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:270)at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:308)at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:472)at com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:111)at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3129)at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:238)at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:93)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394)at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152)at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213)at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195)at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194)at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741)at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863)at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510) For me it seems clear that tiles isn't getting loaded. Do you have any hints for this. Best Regards/Hans 

Express yourself instantly with MSN Messenger! MSN Messenger 

Express yourself instantly with MSN Messenger! MSN Messenger 

Express yourself instantly with MSN Messenger! MSN Messenger 

Express yourself instantly with MSN Messenger! MSN Messenger 
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Re: struts-tiles migration issues

Posted by Antonio Petrelli <an...@gmail.com>.
First of all it is not the same problem as the TILES-201 issue.
>From your stacktrace I suppose that you are trying to render the
".welcomeat" tiles definition. Check if:
- you have this definition in your tiles-defs.xml
- Tiles loads correctly the Tiles definition files at startup (i.e. check
the log at startup).
- possibly, use type="definition" when you put the attribute, if it still
does not work.

Antonio