WebSphere Virtual Enterprise (formerly Operations Optimization), Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Tuning ODR maximum connections

Increasing ODR maximum connections per server allows for more connections to be created and pooled, and enables keeping connections for a significant amount of time.

Before you begin

Modify your JVM heap settings. See Modifying the JVM heap size for the on demand router .

About this task

To enable keeping connections for a significant time, the ODR maximum connections per server should be increased to allow for more connections to be created and pooled. The ODR allocates connections beyond the setting specified, but will not pool those connections when they are returned to the pool if the pool already contains this amount of idle connections. A general setting for the maximum connections per server can be calculated as the peak number of concurrent clients divided by the number of servers allotted for an application. For dynamic server clusters, the number of servers is the minimum number of servers the cluster is defined to.

The following steps show you how to adjust the application server's maximum connections per server. From the administrative console:

Procedure

  1. Click Servers > On Demand Routers odr_name > On Demand Router Properties > On Demand Router Settings.
  2. Use the calculation described previously and enter your result in the maximum connections per server field.



Related tasks
Creating and configuring ODRs
Modifying the JVM heap size for the on demand router
Tuning ODR persistent requests
Tuning the on demand router (ODR)
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 6:17:06 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/odoe_task/todrconnect.html