Fiddling with JProbe 8.3

I was encountering an "OutOfMemory" issue in one of my Java projects. Out of curiousity, I wanted to delve deep and get to the bottom of it.

I downloaded the latest JProbe 8.3 and was going through the tutorial videos, samples, documentation material, and what not.

Our project is a SOA project involving Web Tier, Business Tier and Data tier. I wanted to test out all the various tiers end-to-end and come up with a report of all the memory-leaking spots.

It is always ideal to integrate JProbe with the IDE. This would immensely help the probing exercise. After you have deployed all your applications, you can run an end-to-end test case and monitor through JProbe.

The first step would be to configure JProbe. Follow the documented steps and configure JProbe for your particular App Server. Our app server is Weblogic Server.

Second, integrate the JProbe with your App Server. First, a backup of the existing startWebLogic.sh file. Then JProbe creates another startWebLogic.sh file where it modifies some parameters based on your JProbe configuration performed in step 1.

Then you can launch JProbe via that script. You would see that JProbe monitors everything pertaining to that server.

I was sailing smoothly until this point. Life was all great!!

The next step for me was to integration JProbe 8.3 with our IDE. Our IDE is JDev 11g. I had a shocker here. It seems beginning JProbe 8.x, the support for JDev IDE integration has been dropped! This was a bummer!

JDev was one of the supported IDEs for JProbe integration in earlier releases like JProbe 7.x, etc.

In JProbe 8.x, they support Eclipse integration. But they have dropped JDev. Unbelievable !

This is a bit of a blow. Looks like JDev is being marooned! Is it because as a development platform, JDev is losing market share?