public class ProxoolConnectionProvider extends Object implements ConnectionProvider
ConnectionProvider,
Serialized Form| Modifier and Type | Field and Description |
|---|---|
static ProxoolMessageLogger |
LOG |
| Constructor and Description |
|---|
ProxoolConnectionProvider() |
| Modifier and Type | Method and Description |
|---|---|
void |
close()
Release all resources held by this provider.
|
void |
closeConnection(Connection conn)
Dispose of a used connection.
|
void |
configure(Properties props)
Initialize the connection provider from given properties.
|
Connection |
getConnection()
Grab a connection
|
boolean |
isUnwrappableAs(Class unwrapType)
Can this wrapped service be unwrapped as the indicated type?
|
boolean |
supportsAggressiveRelease()
Does this connection provider support aggressive release of JDBC
connections and re-acquisition of those connections (if need be) later?
This is used in conjunction with
AvailableSettings.RELEASE_CONNECTIONS
to aggressively release JDBC connections. |
<T> T |
unwrap(Class<T> unwrapType)
Unproxy the service proxy
|
public static final ProxoolMessageLogger LOG
public Connection getConnection() throws SQLException
getConnection in interface ConnectionProviderSQLExceptionpublic boolean isUnwrappableAs(Class unwrapType)
WrappedisUnwrappableAs in interface WrappedunwrapType - The type to check.public <T> T unwrap(Class<T> unwrapType)
Wrappedpublic void closeConnection(Connection conn) throws SQLException
closeConnection in interface ConnectionProviderconn - a JDBC connectionSQLExceptionpublic void configure(Properties props) throws HibernateException
props - SessionFactory propertiesHibernateExceptionpublic void close()
throws HibernateException
HibernateExceptionpublic boolean supportsAggressiveRelease()
ConnectionProviderAvailableSettings.RELEASE_CONNECTIONS
to aggressively release JDBC connections. However, the configured ConnectionProvider
must support re-acquisition of the same underlying connection for that semantic to work.
Typically, this is only true in managed environments where a container
tracks connections by transaction or thread.
Note that JTA semantic depends on the fact that the underlying connection provider does
support aggressive release.supportsAggressiveRelease in interface ConnectionProvidertrue if aggressive releasing is supported; false otherwise.ConnectionProvider.supportsAggressiveRelease()Copyright © 2001-2013 Red Hat, Inc. All Rights Reserved.