@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class ConnectionPoolConfiguration extends Object implements Serializable, Cloneable
 Specifies the settings that control the size and behavior of the connection pool associated with a
 DBProxyTargetGroup.
 
| Constructor and Description | 
|---|
| ConnectionPoolConfiguration() | 
| Modifier and Type | Method and Description | 
|---|---|
| ConnectionPoolConfiguration | clone() | 
| boolean | equals(Object obj) | 
| Integer | getConnectionBorrowTimeout()
 The number of seconds for a proxy to wait for a connection to become available in the connection pool. | 
| String | getInitQuery()
 One or more SQL statements for the proxy to run when opening each new database connection. | 
| Integer | getMaxConnectionsPercent()
 The maximum size of the connection pool for each target in a target group. | 
| Integer | getMaxIdleConnectionsPercent()
 Controls how actively the proxy closes idle database connections in the connection pool. | 
| List<String> | getSessionPinningFilters()
 Each item in the list represents a class of SQL operations that normally cause all later statements in a session
 using a proxy to be pinned to the same underlying database connection. | 
| int | hashCode() | 
| void | setConnectionBorrowTimeout(Integer connectionBorrowTimeout)
 The number of seconds for a proxy to wait for a connection to become available in the connection pool. | 
| void | setInitQuery(String initQuery)
 One or more SQL statements for the proxy to run when opening each new database connection. | 
| void | setMaxConnectionsPercent(Integer maxConnectionsPercent)
 The maximum size of the connection pool for each target in a target group. | 
| void | setMaxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
 Controls how actively the proxy closes idle database connections in the connection pool. | 
| void | setSessionPinningFilters(Collection<String> sessionPinningFilters)
 Each item in the list represents a class of SQL operations that normally cause all later statements in a session
 using a proxy to be pinned to the same underlying database connection. | 
| String | toString()Returns a string representation of this object. | 
| ConnectionPoolConfiguration | withConnectionBorrowTimeout(Integer connectionBorrowTimeout)
 The number of seconds for a proxy to wait for a connection to become available in the connection pool. | 
| ConnectionPoolConfiguration | withInitQuery(String initQuery)
 One or more SQL statements for the proxy to run when opening each new database connection. | 
| ConnectionPoolConfiguration | withMaxConnectionsPercent(Integer maxConnectionsPercent)
 The maximum size of the connection pool for each target in a target group. | 
| ConnectionPoolConfiguration | withMaxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
 Controls how actively the proxy closes idle database connections in the connection pool. | 
| ConnectionPoolConfiguration | withSessionPinningFilters(Collection<String> sessionPinningFilters)
 Each item in the list represents a class of SQL operations that normally cause all later statements in a session
 using a proxy to be pinned to the same underlying database connection. | 
| ConnectionPoolConfiguration | withSessionPinningFilters(String... sessionPinningFilters)
 Each item in the list represents a class of SQL operations that normally cause all later statements in a session
 using a proxy to be pinned to the same underlying database connection. | 
public void setMaxConnectionsPercent(Integer maxConnectionsPercent)
 The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is expressed as a
 percentage of the max_connections setting for the RDS DB instance or Aurora DB cluster used by the
 target group.
 
Default: 100
Constraints: between 1 and 100
maxConnectionsPercent - The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is
        expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora DB
        cluster used by the target group.
        Default: 100
Constraints: between 1 and 100
public Integer getMaxConnectionsPercent()
 The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is expressed as a
 percentage of the max_connections setting for the RDS DB instance or Aurora DB cluster used by the
 target group.
 
Default: 100
Constraints: between 1 and 100
max_connections setting for the RDS DB instance or Aurora
         DB cluster used by the target group.
         Default: 100
Constraints: between 1 and 100
public ConnectionPoolConfiguration withMaxConnectionsPercent(Integer maxConnectionsPercent)
 The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is expressed as a
 percentage of the max_connections setting for the RDS DB instance or Aurora DB cluster used by the
 target group.
 
Default: 100
Constraints: between 1 and 100
maxConnectionsPercent - The maximum size of the connection pool for each target in a target group. For Aurora MySQL, it is
        expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora DB
        cluster used by the target group.
        Default: 100
Constraints: between 1 and 100
public void setMaxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
 Controls how actively the proxy closes idle database connections in the connection pool. A high value enables the
 proxy to leave a high percentage of idle connections open. A low value causes the proxy to close idle client
 connections and return the underlying database connections to the connection pool. For Aurora MySQL, it is
 expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora DB
 cluster used by the target group.
 
Default: 50
 Constraints: between 0 and MaxConnectionsPercent
 
maxIdleConnectionsPercent - Controls how actively the proxy closes idle database connections in the connection pool. A high value
        enables the proxy to leave a high percentage of idle connections open. A low value causes the proxy to
        close idle client connections and return the underlying database connections to the connection pool. For
        Aurora MySQL, it is expressed as a percentage of the max_connections setting for the RDS DB
        instance or Aurora DB cluster used by the target group. 
        Default: 50
        Constraints: between 0 and MaxConnectionsPercent
public Integer getMaxIdleConnectionsPercent()
 Controls how actively the proxy closes idle database connections in the connection pool. A high value enables the
 proxy to leave a high percentage of idle connections open. A low value causes the proxy to close idle client
 connections and return the underlying database connections to the connection pool. For Aurora MySQL, it is
 expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora DB
 cluster used by the target group.
 
Default: 50
 Constraints: between 0 and MaxConnectionsPercent
 
max_connections setting for the RDS DB
         instance or Aurora DB cluster used by the target group. 
         Default: 50
         Constraints: between 0 and MaxConnectionsPercent
public ConnectionPoolConfiguration withMaxIdleConnectionsPercent(Integer maxIdleConnectionsPercent)
 Controls how actively the proxy closes idle database connections in the connection pool. A high value enables the
 proxy to leave a high percentage of idle connections open. A low value causes the proxy to close idle client
 connections and return the underlying database connections to the connection pool. For Aurora MySQL, it is
 expressed as a percentage of the max_connections setting for the RDS DB instance or Aurora DB
 cluster used by the target group.
 
Default: 50
 Constraints: between 0 and MaxConnectionsPercent
 
maxIdleConnectionsPercent - Controls how actively the proxy closes idle database connections in the connection pool. A high value
        enables the proxy to leave a high percentage of idle connections open. A low value causes the proxy to
        close idle client connections and return the underlying database connections to the connection pool. For
        Aurora MySQL, it is expressed as a percentage of the max_connections setting for the RDS DB
        instance or Aurora DB cluster used by the target group. 
        Default: 50
        Constraints: between 0 and MaxConnectionsPercent
public void setConnectionBorrowTimeout(Integer connectionBorrowTimeout)
The number of seconds for a proxy to wait for a connection to become available in the connection pool. Only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
connectionBorrowTimeout - The number of seconds for a proxy to wait for a connection to become available in the connection pool.
        Only applies when the proxy has opened its maximum number of connections and all connections are busy with
        client sessions.
        Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
public Integer getConnectionBorrowTimeout()
The number of seconds for a proxy to wait for a connection to become available in the connection pool. Only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
public ConnectionPoolConfiguration withConnectionBorrowTimeout(Integer connectionBorrowTimeout)
The number of seconds for a proxy to wait for a connection to become available in the connection pool. Only applies when the proxy has opened its maximum number of connections and all connections are busy with client sessions.
Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
connectionBorrowTimeout - The number of seconds for a proxy to wait for a connection to become available in the connection pool.
        Only applies when the proxy has opened its maximum number of connections and all connections are busy with
        client sessions.
        Default: 120
Constraints: between 1 and 3600, or 0 representing unlimited
public List<String> getSessionPinningFilters()
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
Default: no session pinning filters
public void setSessionPinningFilters(Collection<String> sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
sessionPinningFilters - Each item in the list represents a class of SQL operations that normally cause all later statements in a
        session using a proxy to be pinned to the same underlying database connection. Including an item in the
        list exempts that class of SQL operations from the pinning behavior.
        Default: no session pinning filters
public ConnectionPoolConfiguration withSessionPinningFilters(String... sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
 NOTE: This method appends the values to the existing list (if any). Use
 setSessionPinningFilters(java.util.Collection) or
 withSessionPinningFilters(java.util.Collection) if you want to override the existing values.
 
sessionPinningFilters - Each item in the list represents a class of SQL operations that normally cause all later statements in a
        session using a proxy to be pinned to the same underlying database connection. Including an item in the
        list exempts that class of SQL operations from the pinning behavior.
        Default: no session pinning filters
public ConnectionPoolConfiguration withSessionPinningFilters(Collection<String> sessionPinningFilters)
Each item in the list represents a class of SQL operations that normally cause all later statements in a session using a proxy to be pinned to the same underlying database connection. Including an item in the list exempts that class of SQL operations from the pinning behavior.
Default: no session pinning filters
sessionPinningFilters - Each item in the list represents a class of SQL operations that normally cause all later statements in a
        session using a proxy to be pinned to the same underlying database connection. Including an item in the
        list exempts that class of SQL operations from the pinning behavior.
        Default: no session pinning filters
public void setInitQuery(String initQuery)
 One or more SQL statements for the proxy to run when opening each new database connection. Typically used with
 SET statements to make sure that each connection has identical settings such as time zone and
 character set. For multiple statements, use semicolons as the separator. You can also include multiple variables
 in a single SET statement, such as SET x=1, y=2.
 
Default: no initialization query
initQuery - One or more SQL statements for the proxy to run when opening each new database connection. Typically used
        with SET statements to make sure that each connection has identical settings such as time
        zone and character set. For multiple statements, use semicolons as the separator. You can also include
        multiple variables in a single SET statement, such as SET x=1, y=2. 
        Default: no initialization query
public String getInitQuery()
 One or more SQL statements for the proxy to run when opening each new database connection. Typically used with
 SET statements to make sure that each connection has identical settings such as time zone and
 character set. For multiple statements, use semicolons as the separator. You can also include multiple variables
 in a single SET statement, such as SET x=1, y=2.
 
Default: no initialization query
SET statements to make sure that each connection has identical settings such as time
         zone and character set. For multiple statements, use semicolons as the separator. You can also include
         multiple variables in a single SET statement, such as SET x=1, y=2. 
         Default: no initialization query
public ConnectionPoolConfiguration withInitQuery(String initQuery)
 One or more SQL statements for the proxy to run when opening each new database connection. Typically used with
 SET statements to make sure that each connection has identical settings such as time zone and
 character set. For multiple statements, use semicolons as the separator. You can also include multiple variables
 in a single SET statement, such as SET x=1, y=2.
 
Default: no initialization query
initQuery - One or more SQL statements for the proxy to run when opening each new database connection. Typically used
        with SET statements to make sure that each connection has identical settings such as time
        zone and character set. For multiple statements, use semicolons as the separator. You can also include
        multiple variables in a single SET statement, such as SET x=1, y=2. 
        Default: no initialization query
public String toString()
toString in class ObjectObject.toString()public ConnectionPoolConfiguration clone()