IBM WebSphere Performance Issue

When we are developing large scale application, we have performance issue.

Some time performance issue occurs due to data volume of input. 

Some time performance issue occurs due to wrong input data. 

Some time it occurs due to hardware configurations. 

Some time it occurs due to wrong implementation. 

But 

We can fix performance issue.

Day to day life whatever we are doing; 
we  always have memory of that, in term of java its log............. :).

We generally click pic's from our daily life or in special occasions and make a memory.

Same in java we click Java JVM snapshot in special occasion and make a memory :)

Snap shot can be Thread dump, Heapdump, Coredump.

Here, I am going to describe IBM WebSphere Setting  to generate Threadump, Heapdump, Coredump manually.

In WebSphere Application Server 6.1, we have to register heap dump event with JVM. 

Once its registered with JVM, manually we can generate dump files.

JVM generally requires a Signal[kill -3 (proces id)] 

whenever we want to generate dump files.

It is a kind of trigger, once its fired dump files will be genrated.

Hot to set JVM parameter in IBM WebSphere  server 6.1 

• Server
• Application Servers
• myServer
• Server Infrastructure

After this click on Java and Process Management.

• Java and Process Management
• Process Definition
• Additional Properties
• Java Virtual Machine

add below mentaion string in Generic JVM arguments field:

-Xdump:heap:events=user 

Save configuration and restart application Server

To generate the heapdump, 

Go to unix prompt where server is running. 

Use the "kill" command: kill -3 <java process ID> to genrate dump files.

"IBM Heap Dump Analyser" and "Thread and monitor Dump Analyzer" 

tools generally use for analysis of dump files.

-------------------------------------------------------------------------------