When you deploy Brix-cms under Weblogic you will encounter the following issue or error:
Details of the error are documented here.
We are trying to evaluate using Brix and in the demo when deployed under Weblogic, we’re seeing an issue. But we have been unsuccessful in isolating the problem to one area, namely if it’s Brix or Wicket or Weblogic.
Issue: When we deploy the demo (latest from SVN from Mar. 4th, 2010), under Weblogic - and upon the first request everything works fine. But when we hit refresh (F5) on the index.html page, we see the following errors in the Weblogic console:
The same code deployed against Tomcat works fine. And in researching the issue, it seems that in Weblogic when the Servlet does not set the “Content-Length” appropriately, it throws the above error.
Since I’m not all that familiar with the code, I’m not sure if it’s an issue to be addressed in Wicket or in Brix.
The problem only happens when we refresh the page and in sniffing the HTML headers the following differences were noted between the first request and any consecutive requests where it fails: [REQUEST HEADERS] In IE7: Pragma: no-cache
In FireFox: Cache-Control: max-age=0
When I (using webscrab) intercept and remove the above mentioned headers from my request stream, the page shows up fine.
Some of the results from Google search also pointed out that this may be as a result of trying to fetch a cached content that’s GZIPed.
Has anyone out there deployed Brix in Weblogic or has anyone encountered a similar issue in Weblogic???
The same code (WAR file) works fine in Tomcat but not in Weblogic.
Also I believe it’s unique to Weblogic+Wicket+Brix because of the nature of Brix serving the resources as opposed to the web container serving the content.
Any help is greatly appreciated?
One additional observation we made is this (and this may shed some light on the problem):
Within Brix the “home page” refers to a page named “index.html”. Which has the following dependencies:
index.html + |___ css/style1.css |___ ../images/bg1.jpg |___ ../images/header.png |___ ../images/main-menu-bg.png
When we created a new page in the Brix content repository under the name “index.do” with no templates attached (the additional dependencies with the .css and .jpg and .png are no longer there) and fetched it via this: http://localhost/brixdemo/index.do
The page worked fine and when we did a F5 to refresh, there were NO ERRORS.
Next we applied template “/includes/template-with-right-menu.html” to that same page and loaded up the page. And this time each of the request for resources such as the style1.css and .jpg’s and .png’s threw the same error upon refresh.
So based on this behavior, Weblogic must somehow treat a consecutive request for the same content differently. And some where in where it treats each mime-type, it must treat the “*.do”s differently compared to a “.css” or a “.html”.
Does anyone have any suggestions on how to deal with this issue???
Here’s more of my findings:
When deployed under Weblogic after a restart when I request this:
Request-1: http://localhost/brixdemo/images/header.png > works fine and I get the image Request-2: http://localhost/brixdemo/images/header.png > (Refresh) Throws the error defined in my main email and I get zero bytes back. Request-3: http://localhost/BPortal/images/header.png?foo=bar > notice the additional parameters I’m passing in - works once again Request-4: http://localhost/BPortal/images/header.png?foo=bar > (refresh) - once again, I get the error on Weblogic and zero bytes sent back. Request-5: http://localhost/BPortal/images/header.png?foo=bar2 > once again works.
So it seems that something different happens when deployed in Weblogic and a request for cached content is requested.
Any help you can offer is greatly appreciated.
And when you search in Google for “Weblogic Didn’t meet stated Content-Length”, you will find tons of others who have encountered a similar issue.
Well here’s a fix that can help you get by without addressing the issue with Oracle Weblogic.
Modify the following file:
Commented out the line that says the following: //Line. 98 response.setContentLength(node.getContentLength()); // below the following line and recompile and deploy code // if (d.after(lastModified) || d.toString().equals(lastModified.toString()))
And that should take care of this issue.