[jboss-jira] [JBoss JIRA] (WFLY-2919) PostgreSQL check-valid-connection-sql doesn't work

[Sean Hsien (JIRA)]

Sean Hsien created WFLY-2919:
--------------------------------

             Summary: PostgreSQL check-valid-connection-sql doesn't work
                 Key: WFLY-2919
                 URL: https://issues.jboss.org/browse/WFLY-2919
             Project: WildFly
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: JCA
    Affects Versions: 8.0.0.Final
         Environment: Windows 7, PostgreSQL 9.3beta2, PostgreSQL JDBC driver 9.3-1100, Spring framework 3.1.2
            Reporter: Sean Hsien
            Assignee: Jesper Pedersen


The {code:xml}<check-valid-connection-sql>{code} doesn't work. After starting my app, I shutdown postgres, then restart it. After restarting Wildfly continues to report the connection is closed. Note that the same test works as expected in JBoss AS 7.1.0. Below is an extract of my standalone.xml for my datasource:

{code:xml}
<datasource jta="true" jndi-name="java:jboss/datasources/testdb" pool-name="testdb" enabled="true" spy="true" use-ccm="true">
	<connection-url>jdbc:postgresql://localhost:5432/testdb</connection-url>
	<driver>postgresql-9.3-1100.jdbc41.jar</driver>
	<pool>
		<min-pool-size>0</min-pool-size>
		<max-pool-size>1</max-pool-size>
		<use-strict-min>true</use-strict-min>
		<flush-strategy>FailingConnectionOnly</flush-strategy>
	</pool>
	<security>
		<user-name>user</user-name>
		<password>password</password>
	</security>
	<validation>
		<check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
		<background-validation>false</background-validation>
		<background-validation-millis>1000</background-validation-millis>
	</validation>
	<statement>
		<prepared-statement-cache-size>0</prepared-statement-cache-size>
		<share-prepared-statements>false</share-prepared-statements>
	</statement>
</datasource>
{code}

I've tried deploying the postgres jdbc driver in 2 ways: via the module and also by copying the jar directly into the standalone/deployments folder, both ways having the same error.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira