[
https://wso2.org/jira/browse/WSAS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Afkham Azeez updated WSAS-805:
------------------------------
Assignee: sumedha rubasinghe (was: Afkham Azeez)
Thanks for this feature suggestion. We will see whether we can get this into
the forthcoming WSAS release. Sumedha, we would like to have you expert opinion
on this.
Thanks
Azeez
> extend jdbc connection pool parameters for a dataservice
> --------------------------------------------------------
>
> Key: WSAS-805
> URL: https://wso2.org/jira/browse/WSAS-805
> Project: WSO2 WSAS
> Issue Type: Improvement
> Components: data-services
> Affects Versions: 2.3
> Reporter: Martijn Smit
> Assignee: sumedha rubasinghe
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> For a jdbc connection pool for a dataservice the only possible
> pool-parameters now are minpoolsize and maxpoolsize. To gain more control
> over the health status of connections in the pool we like to have the
> possibility to set more parameters, like:
> * parameter to set milliseconds to check idle connections:
> This can be done by using the method setTestWhileIdle (in combination with
> the method setTimeBetweenEvictionRunsMillis) from the class GenericObjectPool
> (which is used to setup a pool).
> *parameter to set a validation query.
> This can be done by using the method setValidationQuery from the class
> PoolableConnectionFactory.
> Is it possible to implement this ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
