Other key configurations required for performance tuning of your Enterprise Web Platform include the $JBOSS_HOME/server/$PROFILE/deployers/jbossweb.deployer/server.xml file that sets your HTTP requests pool.

JBoss Enterprise Web Platform 5 has a robust thread pooling, that should be sized appropriately. The server has a jboss-service.xml file in the $JBOSS_HOME/server/$PROFILE/conf directory that defines the system thread pool. There is a setting that defines the behavior if there isn't a thread available in the pool for execution. The default is to allow the calling thread to execute the task. You can monitor the queue depth of the system thread pool through the JMX Console, and determine from that if you need to make the pool larger.

The new administration console can be used for configuring and managing different aspects of the Enterprise Web Platform environment.

The default configuration is appropriate for development, but not necessarily for a production environment. In the default configuration, console logging is enabled. Console logging is ideal for development, especially within the IDE, as you get all the log messages to show in the IDE console view. In a production environment, console logging is very expensive and is not recommended. Turn down the verbosity level of logging if its not necessary. Please note that the less you log, the less I/O will be generated, and the better the overall throughput will be.

Other performance tuning aspects include Caching, Clustering and Replication which are discussed in the respective Chapters in this book.