> # Jolt Connection Pools

> Column Display Related Tasks

> Jolt is a Java-based client API that manages requests from generic Java clients and applications on any Java EE Web server to Oracle Tuxedo services. Jolt connection pools enable applications on WebLogic Server to connect to Oracle Tuxedo domains.

> This page summarizes the Jolt connection pools that have been configured in the current WebLogic Server domain.

> The Jolt API is embedded within the WebLogic Server API and is accessible from a servlet or any other application running on WebLogic Server. Each WebLogic Server instance creates its Jolt connection pools at startup and assigns connections to servlets or applications as needed. The connection pool connects to Oracle Tuxedo via a Jolt Service Listener (JSL), which runs on the Tuxedo server.

> #### Column Display

> You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

> The following table lists all of the data points that you can display in columns on this page.

> Name | Description
> --- | ---
> Name | The name of this Jolt connection pool. MBean Attribute: `JoltConnectionPoolMBean.Name` Changes take effect after you redeploy the module or restart the server.
> Targets | A list of current targets for this Jolt connection pool.
> Primary Addresses | The list of addresses for the primary Jolt Server Listeners (JSLs) on the Tuxedo system. The format of each address is: `//hostname:port`. Multiple addresses should be separated by commas. MBean Attribute: `JoltConnectionPoolMBean.PrimaryAddresses`

> Changes take effect after you redeploy the module or restart the server.

> Failover Addresses | The list of Jolt Server Listeners (JSLs) addresses that is used if the connection pool cannot estabilish connections to the Primary Addresses, or if the primary connections fail. The format of each address is: `//hostname:port`. Multiple addresses should be separated by commas.

> These JSLs need not reside on the same host as the primary JSLs.

> MBean Attribute:
> `JoltConnectionPoolMBean.FailoverAddresses`

> Changes take effect after you redeploy the module or restart the server.

> Minimum Pool Size | The minimum number of connections to be added to this Jolt connection pool when WebLogic Server starts. MBean Attribute: `JoltConnectionPoolMBean.MinimumPoolSize` Minimum value: `0` Maximum value: `2147483647`

> Changes take effect after you redeploy the module or restart the server.

> Maximum Pool Size | The maximum number of connections that can be made from this Jolt connection pool. MBean Attribute: `JoltConnectionPoolMBean.MaximumPoolSize` Minimum value: `1` Maximum value: `2147483647`

> Changes take effect after you redeploy the module or restart the server.

> User Role | The Tuxedo user role for this Jolt connection pool. (This is required only when the security level in the Tuxedo domain is `USER_AUTH`, `ACL`, or `MANDATORY_ACL`). MBean Attribute: `JoltConnectionPoolMBean.UserRole` Changes take effect after you redeploy the module or restart the server.
> Security Context Enabled | Indicates whether this Jolt connection pool passes the connection pool's security context (user name, password and other information) from the WebLogic Server user to the Tuxedo domain. If you enable the connection pool to pass the security context, you must start the Jolt Service Handler (JSH) with the `-a` option. When the JSH gets a message with the caller's identity, it calls `impersonate_user()` to get the appkey for the user. JSH caches the appkey, so the next time the caller makes a request, the appkey is retrieved from the cache and the request is forwarded to the service. A cache is maintained by each JSH, which means that there will be a cache maintained for all the session pools connected to the same JSH.

> You must enable Security Context if Tuxedo requires secured connections.

> MBean Attribute:
> `JoltConnectionPoolMBean.SecurityContextEnabled`

> Secure value: `true`

> Changes take effect after you redeploy the module or restart the server.

> RecvTimeout | The Tuxedo user role for this Jolt connection pool. (This is required only when the security level in the Tuxedo domain is `USER_AUTH`, `ACL`, or `MANDATORY_ACL`). MBean Attribute: `JoltConnectionPoolMBean.UserRole` Changes take effect after you redeploy the module or restart the server.
> User Name | A user name that applications specify to connect to this Jolt connection pool. If Security Context is enabled, this name must be the name of an authorized Tuxedo user. (Specifying a Tuxedo user name is required if the Tuxedo authentication level is `USER_AUTH`.)

> MBean Attribute:
> `JoltConnectionPoolMBean.UserName`

> Changes take effect after you redeploy the module or restart the server.

> Related Tasks

> - Connect to Tuxedo with Jolt
> - Monitor Jolt connection pools
> - Reset Jolt connections
> - Delete Jolt connection pools