On 10/20/2014 11:45 AM, Claudio Miranda wrote:
On Mon, Oct 20, 2014 at 12:02 PM, Jesper Pedersen
> :test-connection-in-pool may require credentials, so it will only be
> 'automatic' in some cases.
Hi Jesper, the purpose is to add a "status" runtime attribute to the
datasource, see my initial post.
Instead of call test-connection-in-pool for every datasource change,
better to rely on current behavior, when application requests a new
connection, the status attribute is populated accordingly to the new
connection call, what do you think ?
That is not going to happen, as testing :test-connection-in-pool per
request could have a massive overhead depending on the pool status.
<validation> should be used to verify an active pool.
This is to improve user experience with wildfly/eap customers, to
quickly see in the web console which datasources failed to open
Yes, I know that - but I fail to see how a 'false' value would be of
benefit to the user experience even if the datasource is active and valid.
Standard scenarios: pool is full (check InUse count if statistics is
enabled), missing credentials (pass those in), ...
I would rather see a CLI script that goes through the different
scenarios that could occur and present the result. Same script could be
executed from the web console, or 'hidden' behind a special "Status"