Welcome to the Java Programming Forums

The professional, friendly Java community. 21,500 members and growing!

The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.


Members have full access to the forums. Advertisements are removed for registered users.

Results 1 to 2 of 2

Thread: Monitoring each Java web request

  1. #1
    Junior Member
    Join Date
    May 2012
    Thanked 0 Times in 0 Posts

    Default Monitoring each Java web request


    I am in search for a tool which gives information regarding cpu & memory usage by each url (element) of my live web application.
    The tool should be open source and could be configured in production environment.
    I want to find out which web request when be executed, outofmemory exception will be faced by my web application.

    I'm searching for such a tool from last some days.
    I have found jeeobserver which gives me info. regarding cpu usage but information regarding memory usage is not provided.

    Any help/suggestion will be appreciated.

    Namrata Shah

  2. #2
    Super Moderator Sean4u's Avatar
    Join Date
    Jul 2011
    Tavistock, UK
    Thanked 103 Times in 93 Posts

    Default Re: Monitoring each Java web request

    Try obtaining heapdumps (with jmap) every few hours, or once per day over the course of a few hours or days, inspecting them with something like jvisualvm. You'll probably spot the cause of the problem more quickly than I replied to your message. OutOfMemoryErrors (OOMEs) on a web application are most likely either a memory leak (references to defunct objects being held longer than they should - easy to spot and inevitable OOME) or some code or library that occasionally demands a surprisingly large amount of memory (harder to spot and may only occur when several uses of the code or library occur concurrently). Try to obtain a heapdump from your webserver *after* the OOME and before you restart it. That isn't always possible, but you may see the smoking gun.

Similar Threads

  1. Java monitoring tool
    By evidentsoftware in forum Java Theory & Questions
    Replies: 1
    Last Post: February 21st, 2012, 09:25 AM
  2. application of monitoring a network in java
    By ola50 in forum Java Networking
    Replies: 0
    Last Post: January 31st, 2012, 12:04 PM
  3. Java - Tutorials done now request assistance?
    By mdiz in forum Java Theory & Questions
    Replies: 2
    Last Post: January 11th, 2012, 02:26 PM
  4. Problem sending POST request with Java..
    By lost in forum What's Wrong With My Code?
    Replies: 3
    Last Post: October 20th, 2010, 09:16 PM
  5. Monitoring program
    By jassi in forum What's Wrong With My Code?
    Replies: 2
    Last Post: February 8th, 2010, 12:29 AM

Tags for this Thread