Thank you very much!
I've fixed it in my jboss-jca.jar and works perfectly.
Thanks! you rule!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025007#4025007
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025007
http://jira.jboss.org/jira/browse/JBAS-4170
This has been resolved in 4.2 and 5.0.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024893#4024893
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024893
The background validation feature only evaluates those connections that are
currently in the pool. The destroy operation removes connections from the pool
and as a result, they are not subject to validation. Can you give me more info
as to why you think it is doing this?
anonymous wrote :
I'm maintaining a pool with 5 connections and validations every minute. On
creation, I assign them an id for monitoring. Here you can see a test case I've
already done:
On startup jboss creates 5 connections (ids 1 to 5), and validates them every
minute. In a given moment, the EIS closes all
Yep. Looks like a bug. I will take care of it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024408#4024408
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024408
___
