This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
We have a simple web-app which we are migrating from weblogic to tomcat.
The datasource configuration is done correctly.
From home page (which gets loaded without any issues), we have Login form.
Upon clicking Login button, we have couple of filters those get called.
And in the Action Class, we have main_frame.html invoked as success target.
This html has 2 jsps as framesets.
The top navigation jsp gets loaded without any issues.
However jsp with main contents comes up empty.
And I see output disabling response for further output in localhost log.
Oct 10, 2011 3:48:02 PM org.apache.catalina.core.ApplicationDispatcher doForward
FINE: Disabling the response for futher output
I am trying to understand what must be happening which is causing no response on UI.
All the logs that I can think of are at FINE level.
I see no application error. Also no exception in any other tomcat logs.
Any pointers on this message and the resolution would be helpful.
I have been struggling to resolve this since few days now.
I have even tried remote debugging. However after ApplicationDispatcher, no output is printed.
However please note: the jsp which I am trying to view is valuated. Its only the output of it is not showing up on UI.
Feel free to ask for any information that might be relevant and I will provide that.
It sound like you have a Struts webapp. Struts is really bad about displaying blank pages when things go wrong inside the application, so I suspect that your log message isn't really an error, just a normal lifecycle indicator for the HTTP request/response cycle.
In other words, yes, at a certain point in the request/response cycle, the response stream is closed for further input so that it can be sent back to the client, and that's normal, not an error. Your real problem is most likely something in the webapp itself that doesn't work properly under Tomcat. And the fun part will be to find out what.
Although in theory J2EE webapps are portable (as long as people don't violate the spec), this theory comes under severe stress when porting to Tomcat, since Tomcat is not a full-stack J2EE server. For example, it doesn't run EJBs or JMS services. If the webapp is depending on one of those missing capabilities, then allowances will have to be made.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Sep 30, 2008
Thanks Tim for the response. We have tried removing all references for weblogic components. Had to take care of the jndi bindings only. Finding if anything is missed.
The strange part is login happens successfully. However the main page which gets loaded after that does not render any of the HTML tags. The top frame has menu and all other tabs show up the contents with exception that CSS doesn't get applied.
Let's see if I get any success further. Trying simple steps and breaking down the code.