Thursday, May 19, 2005

nullpointer on weblogic fixed

I have fixed the problem from my last post, and put the answer here:dev2dev Online

It seems that weblogic was not noticing the changes so it was not redeploying. This is because we are exploding our ear in development. I changed our ant script to always overwrite the META-INF directory containing the application.xml file. This is forcing weblogic to refresh the application correctly (like it would if an entire ear file had changed), and the problem is now gone.

Wednesday, May 18, 2005

Deploy error after recompiling with struts on weblogic

I have posted the same question at BEA's dev2dev Online

We are getting the following stacktrace when hitting the application for the first time after a redeploy. We are running on Weblogic, and the problem goes away after restarting the app or redeploying throught the console. Has anyone seen this before?

at org.apache.struts.action.RequestProcessor.getServletContext(RequestPr
at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(Ti
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja
at org.apache.struts.action.ActionServlet.process(
at org.apache.struts.action.ActionServlet.doGet(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at weblogic.servlet.internal.ServletStubImpl$
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
at weblogic.servlet.internal.TailFilter.doFilter(
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
at com.proprietary.LoggingFilter.doFilter(
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
at com.proprietary.SecurityFilter.doFilter(

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
at weblogic.kernel.ExecuteThread.execute(

Edited 5/19/2004:
I have found a fix, and posted a new entry about it. It dealt with our development deployment using an exploded ear.