Performance and scalability: Weblogic Server 8.1/AIX5.2 Performance goes down after few hour

  1. The performace of the application goes down after 4 to 5 hours of heavy usage. The machine shows high CPU usage by java process. It is in the range of 80 to 90 %. When we re-start weblogic server, everything becomes OK again for next 5 hours. This is a simple JSP/Servlet based application.

    Below are the details of the platform.
    IBM AIX 5.2, Weblogic Server 8.1, Service pack 3,

    Java version:
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX build ca142ifx-20050119 SR1+80507+81622 (JIT enabled: jitc))

    Heap size is 2 GB. Number of threads 8
  2. You should check the memory usage first. Is there any memory leak in your application?
  3. you could try PerformaSure from Quest software....we had a similar problem few month ago where our test box was showing CPU spike and we used this tool to diagnose what it causing spikes....
  4. WebLogic CPU spiking[ Go to top ]

    Hi Shahrukh, Do you remember if Performasure diagnosed database querry timing, server side activities, and garbages collection error or so? Any additional feedback is appreciated. thanks,
  5. You should check the memory usage first. Is there any memory leak in your application?

    Yeah, I also think so. My bet is: after 5 hours, the memory gets full of garbage, so the througput gets down, and the CPU gets crazy, performing all the time garbage collection.

    Use the parameter -verbosegc as an argument for the JVM, and see what happens. I bet you get a lot of full GC after 5 hours.

    Jose Ramon Huerga
  6. We are also facing similar problem. We are running Weblogic 8.1 SP3 on AIX P5 machine. The application slows down after couple of hours of usage and the application response will be very poor or sometime hangs. Does anybody has a fix for this problem?
  7. check the HTTP server - if the HTTP server and application server share a physical machine then the listeners started by the HTTP server impact the CPU of the machine (usually manifesting itself as high system CPU). Either reduce the number of listeners or move the HTTP server to another machine. An excessive number of listeners can also indicate performance problems within the application since an application that responds well will require fewer listeners.