WildFly 8.1.0.Final connection pool recovery

[nickarls]

Hi,

  I'm currently migrating to WF 8.1 and testing connection pool stability by killing of my Oracle DB sessions in order to simulate failures. Apparently I'm a bit too successful since my app never wakes up after that ;-)

In my connection pool I have

                    <pool>

                        <flush-strategy>EntirePool</flush-strategy>

                    </pool>

which I thought would clean up the pool but I still get no DB access when I refresh pages etc. Any suggestions?

I also have

                    <validation>

                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>

                        <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>

                        <exception-sorter class-name="my.custom.ExceptionSorterAllwaysReturningTrue"/>

                    </validation>

                    <timeout>

                        <idle-timeout-minutes>10</idle-timeout-minutes>

                    </timeout>

but that doesn't help.

Thanks in advance,

Nik

[jesper.pedersen]

flush-strategy: You don't want 'EntirePool', you want 'Gracefully'

exception-sorter: org.jboss.jca.adapters.jdbc.extensions.novendor.NullExceptionSorter

validation: Either background-validation or validate-on-match

recovery: org.jboss.jca.core.recovery.ValidatingManagedConnectionFactoryRecoveryPlugin

HTH

[nickarls]

Cool, it works, thanks for the help. You should write your own JCA connector! ;-)

The recovery is for XA-datasources only, right?

and if you have valid-connection-checker and stale-connection-checker there is no need for a check-valid-connection-sql(?)

[jesper.pedersen]

Yeah, I should really find time to look into this JCA thing...

And, correct on both counts.

[melaninforbes]

Thanks a lot. It works