EAServer Transaction Manager  Enhanced systems management support

Chapter 4: New features in EAServer 5.0

Java Connection Management enhancements

The JCM_WAIT, JCM_NOWAIT, and JCM_FORCE flags, which in earlier EAServer versions controlled connection allocation, are no longer used by the JCMCache.getConnection(int) method. You can achieve the same functionality by calling getConnection(0), and configuring the connection cache properties in Table 4-1, using the Caching tab in the Connection Cache Properties dialog box in EAServer Manager.

Table 4-1: Properties to configure connection cache size

Property

Description

Minimum Connection Pool Size

The minimum number of pooled connections, allocated at server start-up. If not set, the default is 0.

With jagtool, you can set as com.sybase.jaguar.conncache.poolsize.min.

Maximum Connections

The absolute maximum number of connections that can be created from the cache. Requests for excess connections either block or fail. A value of 0 indicates that there is no limit.

With jagtool, you can set as com.sybase.jaguar.conncache.poolmanager.maxconnection.

Maximum Connection Pool Sizes

The maximum number of connections that can be cached. If connections are allocated beyond this number, the cache manager drops the excess connections when they are released.

With jagtool, you can set as com.sybase.jaguar.conncache.poolsize.max.

Wait for Connections

When the maximum connections limit is reached, specifies whether requests for excess connections fail immediately or wait until a connection is released. If this setting is enabled, the request waits.

With jagtool, you can set as com.sybase.jaguar.conncache.wait.

For information on tuning these settings, see Chapter 6, “Database Access Tuning,” in the EAServer Performance and Tuning Guide.

Table 4-2 describes three possibilities for configuring connection cache properties to duplicate the functionality that was previously available by passing the JCM flags to JCMCache.getConnection.

Table 4-2: Configuring connection caches

If components previously passed this flag to getConnection

Configure these connection cache property values

JCM_WAIT

Set the value of com.sybase.jaguar.conncache.poolmanager.maxconnections equal to the value of com.sybase.jaguar.conncache.poolsize.max, and set the value of com.sybase.jaguar.conncache.poolmanager.wait to true.

JCM_FORCE

Set the value of com.sybase.jaguar.conncache.poolmanager.maxconnections to 0.

Combination of the two

For easy access to resource connections, set the value of com.sybase.jaguar.conncache.poolmanager.maxconnections to 0.

For more information about these properties, see Appendix B, “Repository Properties Reference,” in the EAServer System Administration Guide.





Copyright © 2005. Sybase Inc. All rights reserved. Enhanced systems management support