Skip to main content

J2EE application profiling with yourkit on Weblogic

One of our provider uses HP-UX on production machine, a few J2ee applications runs on that machine. After sometimes, we start getting complain from our clients that portal often goes out of memory and we decided to investigate the application with Yourkit. Yourkit is a industry leading java profiling software on present day, it can works with standalone java application as well as remote profiling. YourKit supports SQL,JNDI and run time memory profiling, see the following link for more information.

1) First download the version you need, in my cases i download Windows and HP-UX version and got the evaluation key.
2) Unzip the YJP-9.5.3*.zip and run the following command on HP-UX to set the agent for profiling on weblogic
 cd yjp-9.5.3/lib & java -jar yjp.jar -integrate

which will bring up you new command console to configure agent with the weblogic server. Go throws the command prompt and locate your weblogic startup script as follows:

Now you will get a new startup script named startWebLogic_with_yjp.sh to start Weblogic Server with yourkit agent.  Most of all time you can use these script to start WebLogic server with agent, script only contains the  jvm argument

JAVA_OPTIONS="-agentpath:/var/oracle/app/yourkit/yjp-9.5.3/bin/hpux-ia64-64/libyjpagent.so=disablestacktelemetry,disableexceptiontelemetry,builtinprobes=none,delay=10000,sessionname=WebLogicMona
 $JAVA_OPTIONS"
export JAVA_OPTIONS 


On HP-UX these above script couldn't start WebLogic with agent, for some reason env variable JAVA_OPTIONS was not enable on startup terminal. For quick fix i copy the JAVA_OPTIONS on /bin/startWeblogic.sh
and start the server nohup ./startWeblogic.sh &
now in the nohup.out file we found the following log
[YourKit Java Profiler 9.5.3] Loaded. Log file: /home/oracle/.yjp/log/8907.log

From the 8907.log we found the port name which uses agent to connect with.
[YourKit Java Profiler 9.5.3] [12.860]: Profiler agent is listening on port 10001


Now from our host operating system we can connect remotely and profiling our applications.
You can watch demos here to quick start with java YourKit.

Comments

Popular posts from this blog

Apache Ignite deep dive, SQL engine

Apache Ignite  is an open source memory-centric distributed database, caching and comput- ing platform. From the beginning, it was designed as an in-memory data grid for developing a high-performance software system. So, it’s core architecture design is slightly different from the traditional NoSQL databases, which can simplify building modern applications with a flexible data model and simpler high availability, high scalability.     Moreover, to understand how to design application with any databases or framework properly, you must understand the architecture of the database or framework itself. By getting a better idea of the system, you can solve different problems in your enterprise architecture landscape, can select a comprehensive database or framework that is appropriate for your application and get the maximum benefits from the system. In this article we are going to explore the Apache Ignite SQL engine.      Under the hood...

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title  The Apache Ignite book  has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...