More tuning tips on slow Weblogic 10
In the earlier parts of this article I described some technical tuning tips specific to a slow-performing Weblogic JEE server.
Another earlier post has looked at how to set the JSP check seconds values.
This is a follow-up article specifically for tuning the similar settings for Weblogic 10 - since the syntax has changed.
In weblogic.xml, ensure the following are set as below:
<wls:session-descriptor>
<wls:encode-session-id-in-query-params>true</wls:encode-session-id-in-query-params>
<wls:cookie-comment>mysessioncookie</wls:cookie-comment>
<wls:cookie-max-age-secs>-1</wls:cookie-max-age-secs>
<wls:cookie-name>JSESSIONID</wls:cookie-name>
<wls:cookie-path>/</wls:cookie-path>
<wls:cookies-enabled>true</wls:cookies-enabled>
<wls:timeout-secs>1200</timeout-secs>
<wls:cookie-domain>@MY_COOKIE_DOMAIN@</wls:cookie-domain>
</wls:session-descriptor>
Assuming that no JSPs are being hot deployed or dropped directly into the production server
<wls:jsp-descriptor>
<wls:keepgenerated>true</wls:keepgenerated>
<wls:precompile>true</wls:precompile>
<wls:page-check-seconds>-1</wls:page-check-seconds>
</wls:jsp-descriptor>
and this one
<wls:container-descriptor>
<wls:servlet-reload-check-secs>-1</wls:servlet-reload-check-secs>
</wls:container-descriptor>
Ensure all of these are inserted at the right place within the weblogic.xml to avoid any start up error messages
Check against the reference here http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/weblogic_xml.html
Another earlier post has looked at how to set the JSP check seconds values.
This is a follow-up article specifically for tuning the similar settings for Weblogic 10 - since the syntax has changed.
In weblogic.xml, ensure the following are set as below:
<wls:session-descriptor>
<wls:encode-session-id-in-query-params>true</wls:encode-session-id-in-query-params>
<wls:cookie-comment>mysessioncookie</wls:cookie-comment>
<wls:cookie-max-age-secs>-1</wls:cookie-max-age-secs>
<wls:cookie-name>JSESSIONID</wls:cookie-name>
<wls:cookie-path>/</wls:cookie-path>
<wls:cookies-enabled>true</wls:cookies-enabled>
<wls:timeout-secs>1200</timeout-secs>
<wls:cookie-domain>@MY_COOKIE_DOMAIN@</wls:cookie-domain>
</wls:session-descriptor>
Assuming that no JSPs are being hot deployed or dropped directly into the production server
<wls:jsp-descriptor>
<wls:keepgenerated>true</wls:keepgenerated>
<wls:precompile>true</wls:precompile>
<wls:page-check-seconds>-1</wls:page-check-seconds>
</wls:jsp-descriptor>
and this one
<wls:container-descriptor>
<wls:servlet-reload-check-secs>-1</wls:servlet-reload-check-secs>
</wls:container-descriptor>
Ensure all of these are inserted at the right place within the weblogic.xml to avoid any start up error messages
Check against the reference here http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webapp/weblogic_xml.html
Why do you not use
ReplyDeletetrue in your example above? Doesn't this compile your jsps when the application is deployed, as opposed to compiling them when accessed the 1st time? (slower startup -> faster runtime).
Thanks for the site. Its helped alot.
@sw - Indeed we should precompile the JSPs using true. Thanks for pointing out.
ReplyDeleteThat was the setting I used in WL 8 as on this article http://jojovedder.blogspot.com/2009/05/slow-weblogic-response-jsp-and-servlet.html
I have amended this one too. Gotta check my Production settings again