Websphere logs report {0} File not found, but application continues to work without issues

Question

A websphere 6.1 server is running a struts application that seems to be working fine. In the logs, however, I'm seeing the following error message, which is being continually emailed to the support staff.

[3/16/10 15:42:08:089 CDT] 00000023 SystemOut     O FATAL - [03-16-2010 15:42:08] root: The following page could not be found in the Web Administration application. The stack trace follows: 

com.ibm.ws.webcontainer.webapp.WebAppErrorReport: SRVE0190E: File not found: {0}
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:536)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:930)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:524)
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.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
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)

I can narrow down the issue to a single Action and JSP, which are too big to show here, but here's the action definition in struts-config.xml:

    <action
            path="/HappyDefaultThing"
            name="HappyDefaultThingActionForm"
            type="com.foo.webadministration.action.HappyDefaultThingAction"
            validate="true"
            input="/WaAssignDefaultHappyThing.jsp"
            scope="session">
            <forward name="success" path="/WaAssignDefaultHappyThing.jsp"/>
            <forward name="failure" path="/WaAssignDefaultHappyThing.jsp"/>
    </action>

As far as I can see, nothing is missing, and everything necessary is being found, but the logs say "File not found: {0}"

What is "{0}"?? The stack trace only shows IBMs code, which I can't see the source of, and therefore can't trace.

Is this a bug in the websphere code? I'd appreciate any help.

Answer 1

Let's start from the beginning. We need to identify the root cause of the problem. You gave us the exception but left out the cause. Can you please post the error that comes after the exception? You'll see the following message

• Error Page Exception:
• Error Code:
• Target Servlet:
• Error Stack:

Answer 2

Hi, As mentioned by Elite Gentleman, i would expect to see a lot more in the logs than what you have shown here.

https://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webcontainer.resources.Messages.html

FYI: Look at this URL (shown above) for information on the Servlet/Web Container error messages. In this case, it is clear that the Web Container is not able to service out a file.

How did you narrow down the issue to a struts component? The reason i am asking you is this, i don't see any Struts code in the stack trace that you have provided. This effectively implies that this error message is not related to your struts application (or at least the error has occurred prior to the control reaching your struts/web application.

Manglu