WebSphere tips

1. make sure you are using the latest java ibm version in your websphere application , its affect your application performance, you can find your ibm java version like this [websphereroot]/java/jre/java -fullversion

2. If you go to Application servers > server1 > Process Definition > Java Virtual Machine and checked the "Verbose garbage collection " check box , after restarting the server you can see all GC activities in server log directory under file native_stderr.log , to analyse this file you can download an IBM tool from here ->IBM Pattern Modeling and Analysis Tool for Java Garbage Collector

3. In the post i wrote before this one i mention how to get a full trace from your web sphere application , to analyse this trace you can use the next tool from IBM ->IBM Trace and Request Analyzer for WebSphere Application Server

4. To debug your deployed application on websphere follow the next steps:
in the admin console - Application servers > server1 > Process Definition > Java Virtual Machine checked the "Debug Mode " , by doing so the parameters that in the "Debug arguments" text box will be added to the server when restarting , usually the parameters looks like this "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket, server=y,suspend=n,address=7777" , so after restarting your server open your Eclipse (in this case) and you just need to attach to a "remote java application" and put in the server name (where the websphere server is running ) and the port number you set/have from the address (i.e. 7777), and pray :)


5. very good article about java performance on AIX you can find here Maximizing Java performance on AIX

6. here are some WebSphere Tuning links
WebSphere Tuning Tips

WebSphere tuning for the impatient: How to get 80% of the performance improvement with 20% of the effort

Tuning performance

Java virtual machine settings

DB2 tuning parameters

Solving memory problems in WebSphere applications