| Set heap size for groups of servers in a WAS cell |
Set minimum heap size and maximum heap size for an entire class of servers in a WAS cell. Known classes of servers include ApplicationServer, NodeAgent, and CellManager. You can set heap sizes for all servers in a WAS cell by using a class called Server. Optionally, you can enable or disable verbose garbage collection for each server in a class of servers. This script should be safe to run anywhere. It should also work on earlier versions of WAS. |
| Show all the WAS types in a WAS 6.1 cell |
This script should be safe to run anywhere. It should also work on earlier versions of WAS. The number of types it reports is WAS version dependent |
| Show all instances of whatever you WAS type want. |
This script goes through the entire WAS cell and displays the configuration. For a list of the WAS types you can specify, run the wasTypes.py script mentioned above. in a WAS cell. This script requires one command line parameter. That parameter must be the name of a valid WAS type. The name of any WAS type is case sensitive |
| Show the configuration of all the JVMs in a WAS cell |
This script should be safe to run anywhere. I have only tried it on WAS version 6.1 and 7.0 installations |
| Force a heap dump of every JVM in an entire WAS cell without killing any JVMs |
This will consume enormous CPU cycles for an extended period of time on each JVM in an entire cell. This script can easily produce files measured in hundreds of megabytes for each JVM in an entire cell. Think twice before running this on a production cell because of the overhead. This script can require as long as 15 minutes per JVM to execute |
| Force a thread dump of every JVM in an entire WAS cell without killing any JVMs |
This will consume enormous CPU cycles for an extended period of time on each JVM in an entire cell. This script can easily produce files measured in hundreds of megabytes for each JVM in an entire cell. Think twice before running this on a production cell because of the overhead. This script can require as long as 15 minutes per JVM to execute |
