change background-validation-minutes to seconds

[bortx]

Hi,

I have a problem with my jca connector. I want Jboss to validate connections in intervals of seconds (30 sec for example) but the property called background-validation-minutes only allows to specify minutes, so the minimal value is 1 minute. Anyone knows how to specify this property in seconds?

Thanks a lot

Bortx

[adrian.brock]

Feature request:
http://jira.jboss.com/jira/browse/JBAS-4088

[weston.price]

Generally, background validation should occur at longer intervals to avoid stressing the pool. Keep in mind, everytime the background validation cycle begins the entire pool is evaluated.

[bortx]

Yes, you are right, but I have the problem that I have to check connections to the EIS periodically in order to maintain connections. If not, the EIS closes connections not checked. The expiration time is exactly one minute. I use the background validation to perform those checks, so the EIS is constantly closing connections.

One more thing that I've noticed, is that jboss always checks all connections that have been created, the ones that are in the pool at the moment, and the ones that have been destroyed previously. The pool works right, I mean, it never returns a destroyed connection, and the pool has the number of connections I've specified, but I don't know why it tries to validate destroyed connections.

I've implemented the destroy() method so that it closes the connection to the EIS. What actions am I supposed to perform on the destroy() method? May I notify ConnectionEventListener set on some event? I only notify those listeners when in the close() method.

Thanks a lot.

Bortx

[justinwalsh]

Support background-validation-seconds
and deprecate background-validation-minutes

Is this change going to be backported to a 4.2.x release?

Thanks,
Justin

[adrian.brock]

"justinwalsh" wrote:

Support background-validation-seconds
and deprecate background-validation-minutes

Is this change going to be backported to a 4.2.x release?

Thanks,
Justin

Not during 4.2.x releases. That would be an incompatibility in minor point releases.
The change has been made in JBoss5.