Solved

Using JProbe in a clustered Weblogic env.

Posted on 2004-10-12
3
613 Views
Last Modified: 2013-12-10
We have set up a new cluster in our QA area and wish to attach JProbe against it to ensure that some memory leaks have been addressed before we deploy to production. However, all of the JProbe documentation shows JProbe being attached to the startWebLogic.sh script and thus being tied to the starting and stopping of the individual application server.

How do we use JProbe in a clustered weblogic env? Do we attach it to the startManagedServers script on the admin server? Do we somehow attach it to each individual clustered server? We are currently trying to query quest for this information but their documentation is certainly lacking in this area. Any help that can be provided would be most appreciated...

thanks.
0
Comment
Question by:powercrazy
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 3

Accepted Solution

by:
tyags earned 500 total points
ID: 12324865
JProbe and a few other JVM behaviour/memory analysis tools work by attaching agents to the server which they need to probe. So, if you need to use JProbe in cluster you would have to attach your JProbe to each individual managed servers. Hence, the procedure to be followed is going to be same for doing so  i.e. in case of manged server you modify you 'startManagedWeblogic' script file, instead of 'startWelogic' script.

So, the chnages that you would need to make to the script for managed server will be same for eg:-

A. set START_CMD="C:\Program Files\JProbe Suite 5.0.1\bin\jplauncher.exe"

B. set JPLFILE=C:\JProbe\MyTest.jpl

C. %START_CMD% -jp_input=%JPLFILE% %JAVA_VM%

Once the server has started with JProbe settings, you can connect your profiler to individual servers and monitor the behaviour.

It is important to understand that each server has it's own instance of JVM for running the applications. And so JProbe gives you the JVM behaviour on each JVMs, which may or maynot be different unless there is something which has a possibility of going wrong while the managed servers communicate - which in my experience would be a rare case.

The possibility of your application leaking on single node is going to be same/equally-high as the possibility of it leaking in a cluster - since it will behave the same on cluster where it will have it's own instance of JVM.

Hope this helps.

-A.
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

VM backups can be lost due to a number of reasons: accidental backup deletion, backup file corruption, disk failure, lost or stolen hardware, malicious attack, or due to some other undesired and unpredicted event. Thus, having more than one copy of …
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question