Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Reading through the BEA WebLogic 9.2 Deployment Descriptor Elements documentation, there are a few parameters that we already use in our web applications weblogic.xml to decrease the time it takes to run continuous integration tests against WebLogic 9.2:

  • jsp-descriptor, precompile, false
  • jsp-descriptor, page-check-seconds, -1
  • container-descriptor, servlet-reload-check-secs, -1

This is what our weblogic.xml looks like:

<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="" xmlns:xsi=""


Are there are any other usual suspects that we could consider to squeeze out some more life from our build servers?

share|improve this question
Checking if has any useful information. – dezwart Jun 23 '09 at 7:32
Worth noting that the default heap size and nursery space of JRockit is rather limited for enterprise web applications. Bumping this up from the standard 128MB to 2GB increased throughput by 15% and reduced the noise from verbosegc. – dezwart Jun 23 '09 at 23:32
up vote 0 down vote accepted

I can suggest to use performance analyzer for JMX Weblogic statistics. We use HLC by DBA InfoPower ( to merge JMX statistics with database and OS performance data to get overall picture and deep dive analysis into root causes of performance degradation.

share|improve this answer
That sounds like a great start, thanks Sarit. – dezwart Jun 23 '09 at 23:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.