Details
-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.1.2
-
None
-
Documentation (Ref Guide, User Guide, etc.)
-
-
Documented as Resolved Issue
-
NEW
Description
<background-validation> and <background-validation-minutes> have been deprecated and no longer supported by the change of JBAS-4088. <background-validation-minutes> is replaced with <background-validation-millis>. And any <background-validation-millis> > 0 will enable background validation.
So please change <background-validation> from:
Background connection validation reduces the overall load on the RDBMS system when validating a connection. When using this feature, EAP checks whether the current connection in the pool a separate thread (ConnectionValidator). <background-validation-minutes> depends on this value also being set to TRUE. Defaults to FALSE.
to:
This parameter has been deprecated and no longer supported. Any background-validation-millis > 0 will enable background validation.
And also please change <background-validation-minutes> from:
How often, in minutes, the ConnectionValidator runs. Defaults to 10 minutes.
Note:
You should set this to a smallervalue than <idle-timeout-minutes>, unless you have specified <min-pool-size> a minimum pool size set.
to:
This parameter has been deprecated and no longer supported. Use background-validation-millis instead.
And also, please add the following:
Default to 0 mills. And Any background-validation-millis > 0 will enable background validation.
to <background-validation-millis> like:
Background connection validation reduces the overall load on the RDBMS system when validating a connection. Setting this parameter means that JBoss will attempt to validate the current connections in the pool as a separate thread ( ConnectionValidator). This parameter's value defines the interval, in milliseconds, for which the ConnectionValidator will run. (This value should not be the same as your <idle-timeout-minutes value.) Default to 0 mills. Any background-validation-millis > 0 will enable background validation.
