I am trying to debug a really strange problem. Intermittently, a particular JSP will not send down all of the HTML for the screen. When this does happen, it always stops at the exact same point. The browser will clock for a long period of time (much longer than it normally takes the screen to load) and then the incomplete HTML comes back.
I have been trying to find any evidence of an exception getting thrown by increasing the JSPWriter buffer size to insanely huge values and searching through the logs but I am stumped. Can anyone point me in the right direction? This JSP is running on Websphere 6.1 if that makes a difference.
Bear Bibeault wrote:That indeed has all the hallmarks of an exception being thrown during processing.
Nothing in any of the logs?
I see nothing that is immediately obvious. I do see something that looks a little suspicious though. I turned on full tracing for com.ibm.ws.jsp.* classes in Websphere. I don't have access to the log file at the moment but earlier I saw some output regarding /error.jsp. It appeared to be output from the code that checks to see if there are any updates to .jsp source for regenerating the java code.
The interesting thing is that there is no /error.jsp page in my application and as far as I know. That URL does not match the standard error page URL for the application (or page for that matter).
Maybe I should post those details in the Websphere specific forum?