Spring 2.5 and Tiles 2 config issue in Websphere 6.1

[rajakri]

Hi All,
I am trying to migrate an application using Sprig 2.5.0 and Tiles 2 under Websphere 6.1 which gives me the below exception .Kindly note the same web application works fine under Tomcat 5.5 container.

Any help to resolve this issue would be greatly appreciated.

ApplicationContext.xml contains

<!-- Tiles Configuration -->
<bean id="tilesConfigurer"
class="org.springframework.web.servlet.view.tiles2 .TilesConfigurer">
<property name="definitions"
value="/WEB-INF/tiles/tiles-def.xml" />
</bean>

<bean id="viewResolverTiles"
class="org.springframework.web.servlet.view.UrlBas edViewResolver">
<property name="order" value="2" />
<property name="viewClass"
value="org.springframework.web.servlet.view.tiles2 .TilesView" />
</bean>
----------------------------------------------------------------------------------

[6/16/08 9:12:00:914 EST] 00000024 SystemOut O 2008-06-16 09:12:00,487 ERROR [org.apache.tiles.jsp.taglib.RenderTagSupport] - Error during rendering
javax.servlet.jsp.JspException: TilesContainer not initialized
at org.apache.tiles.jsp.taglib.ContainerTagSupport.do StartTag(ContainerTagSupport.java:72)
at org.apache.tiles.jsp.taglib.RenderTagSupport.doSta rtTag(RenderTagSupport.java:146)
at com.ibm._jsp._authenticate._jspx_meth_tiles_insert Template_0(_authenticate.java:156)
at com.ibm._jsp._authenticate._jspService(_authentica te.java:97)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJsp Base.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1068)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:543)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:478)
at com.ibm.wsspi.webcontainer.servlet.GenericServletW rapper.handleRequest(GenericServletWrapper.java:12 2)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensio nServletWrapper.handleRequest(AbstractJSPExtension ServletWrapper.java:225)
at com.ibm.ws.webcontainer.servlet.CacheServletWrappe r.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:115)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:454)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:383)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:263)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminators(NewConnectionIniti alReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncCha nnelFuture.java:205)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1473)

[rajakri]

This was caused due to Connectivity issue to DB in my organisation.Once this got resolved tiles was intialized properly.