glog.vpd Properties

glog.vpd.cache.pinTransactionalConnections

6.3

When pinning connections to the current thread, by default, only non-transactional connections are pinned. To enable transactional connection caching, set this property to true.

glog.vpd.cache.t2SharedConnection.checkDedicatedConnectionIntegrity

21C

If set to true, each dedicated pool connection is checked when released back to the pool. If the user is no longer DBA.ADMIN, the connection has been corrupted. The system will log an exception to narrow down the process that caused the corruption. The user will also be set back to DBA.ADMIN to ensure the connection is healthy for further uses. This property is false by default, to avoid the additional overhead on each connection release. It can be modified in the CUSTOM property set.

glog.vpd.cache.t2SharedConnection.debugLogging

Specifies whether additional debug-level logging of T2SharedConnection reference changes should be logged.

Note that the JDBC logging category must also be enabled, or this property will have no effect.

glog.vpd.cache.usePinnedConnections

6.3

You can pin connections by user to the current thread. This reduces the need to set the VPD user within a single thread. To turn on connection pinning, set this property to true.

By default, only non-transactional connections are pinned.

glog.vpd.cacheByMachine

Unused.

glog.vpd.cacheDebug

If specified, causes the T2SharedConnection cache to verify that VPD users match between the OTM application and the database connection for connection caches. Mismatches will cause T2CachedUserMismatch errors to be logged in the exception log. Only meaningful if connection-mode profile tagging is being used (see glog.vpd.cacheMode.profileTagging property).

glog.vpd.cacheMode.profileTagging

A bitmask in the decimal range 0 to 15, specifying for which T2SharedConnection caching modes that the current user should be attached to the connection. The bit values are: 1 for connection caching, 2 for transaction caching, 4 for VPD caching, and 8 for pool caching. This last code should only be used if WebSphere is the webapp container.

glog.vpd.cacheMode.setUser

6.3

Controls how users are cached. The options are:

• transaction: cache the user in the current transaction properties. This is the default.
• connection: cache the user in the open connections TypeMap. Not recommended for use.
• vpd: queries the current user from the session.

If left blank, the system does not cache the user.