Looking for J2EE diagnostics tool

Discussions

General J2EE: Looking for J2EE diagnostics tool

  1. Looking for J2EE diagnostics tool (5 messages)

    We're in the rollout process of a fairly complex J2EE app running primarily on WebSphere 5.1 (also some .NET front-end components), however we're experiencing some nasty problems (slow transactions, lost transactions...) in the staging lab. We are looking for a tool to help us get to the bottom of these problems. Ideally we would want to use the same tool in production, assuming the overhead is reasonable. We saw a webcast of Mercury Deep Diagnostics, but are unceratin about what it would it take to set it up and deploy (not to mention the $$$$). Anyone had experience with the Mercury tool? other tools? Please Help!!

    Thanks,
    Roy.

    Threaded Messages (5)

  2. Looking for J2EE diagnostics tool[ Go to top ]

    We're in the rollout process of a fairly complex J2EE app running primarily on WebSphere 5.1 (also some .NET front-end components), however we're experiencing some nasty problems (slow transactions, lost transactions...) in the staging lab. We are looking for a tool to help us get to the bottom of these problems. Ideally we would want to use the same tool in production, assuming the overhead is reasonable. We saw a webcast of Mercury Deep Diagnostics, but are unceratin about what it would it take to set it up and deploy (not to mention the $$$$). Anyone had experience with the Mercury tool? other tools? Please Help!!Thanks,Roy.

    Hi Roy

    try using Optimizerit from borland it is available for 15 days evaluation also.

    It is very good tool to obtain and analyse java object stat.
    also you can use Jprofiler or Jprobe.

    I have used above tools not the one which you named.

    Bye

    -Prashant
    -
  3. Looking for J2EE diagnostics tool[ Go to top ]

    We're in the rollout process of a fairly complex J2EE app running primarily on WebSphere 5.1 (also some .NET front-end components), however we're experiencing some nasty problems (slow transactions, lost transactions...) in the staging lab. We are looking for a tool to help us get to the bottom of these problems. Ideally we would want to use the same tool in production, assuming the overhead is reasonable. We saw a webcast of Mercury Deep Diagnostics, but are unceratin about what it would it take to set it up and deploy (not to mention the $$$$). Anyone had experience with the Mercury tool? other tools? Please Help!!Thanks,Roy.

    Hi Roy
    Use this
    http://www.quest.com/APM_Suite_for_the_J2ee_Platform/
    there are different tools that might suit your need.

    Regards
    B S Reddy
  4. Try PerformaSure[ Go to top ]

    If you're looking for a tool that can be used both in test and production environments (without too much overhead), I would recommend trying Quest PerformaSure. This is especially useful if you're tackling performance issues (which apparently you are :-) ). We've used it several times on different projects on different platforms (WebSphere, WebLogic), and it helped us pinpoint the problems in no time.
    Raz
  5. RE: Try PerformaSure[ Go to top ]

    Thanks for the feedback everyone! We did use JProbe for some optimizations, but it failed to work in our load test environment. We haven't tried Performasure yet. The reason we're looking at the Mercury tool is that it is (supposedly) integrated with Loadrunner and Topaz, which we are currently using. Also, they claim it can help with more than just performance problems. However we get the feel that the product is immature, and may take sunstantial efforts to setup. Any additional input would be appreciated!

    Thanks,
    Roy.
  6. Mercury Diagnostics[ Go to top ]

    The overhead for Mercury's tool is probabaly the lowest out of any of the competing tools out there. The nice thing is that it is _extremely_ easy to integrate with LoadRunner and Topaz, if you already have those installed - Deep Diagnostics has the best breadth and depth for any product which may be used to diagnose production applications (and it's been around for 5+ years, but hasn't been marketed to developers very well). All 3 products use the same probe, and configuration for reporting data to all 3 tools is pretty straightforward. If you are looking for some additional guidance, please feel free to contact me directly:
    clay at j2ee911 dot com - my company provides emergency performance tuning services and consulting for production applications and specialize in Mercury's tools. I was previously a performance consultant for them, and if noting else can provide a bit of guidance even if you decide to go with another tool.

    Cheers!
    Clay