Installation guide

CHAPTER 5 New features in EAServer 5.0
What’s New 27
The EAServer Transaction Manager enables EAServer to control the scope and
duration of transactions across multiple resource managers. It also provides the
ability to synchronize transactions and to communicate with other transaction
managers using CORBA OTS.
For more information about this feature, see Chapter 2, “Understanding
Transactions and Component Lifecycles,” in the EAServer Programmer’s
Guide.
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 5-1, using the Caching tab in the Connection Cache Properties dialog
box in EAServer Manager.
Table 5-1: Properties to configure connection cache size
For information on tuning these settings, see Chapter 6, “Database Access
Tuning,” in the EAServer Performance and Tuning Guide.
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.