This section discusses tuning database connection properties. PortalDB should be tuned to handle user load, but you can also modify the database connection properties for any entry in server.xml.
The maxActive, maxIdle, and maxWait properties in the SYBASE\tomcat\ conf\server.xml file define the data connections from the Web application to the PortalDB.
maxActive – defines the maximum number of database connections that should be allowed for PortalDB. This number should be set to a value that reflects the maximum expected user load for the UA 8.0 application.
maxIdle – defines the maximum number of idle database connections that should be available at all times. This number should be set to a value that reflects expected user load fluctuation for the UA 8.0 application.
maxWait – defines the maximum length of time to wait for a database connection. If additional connections are requested that exceed the maxActive property, the additional connections are put into a wait state until an available connection is returned to the pool. maxWait throws an exception when the defined time is exceeded while waiting for an available connection to be returned to the pool.
