[teiid-issues] [JBoss JIRA] (TEIID-4696) Teiid datasource driver does not reconnect after socket is closed

[Rafael Coutinho (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rafael Coutinho closed TEIID-4696.
----------------------------------


Great converting the datasource to the below it fixed it: 

{code:java}
<datasource jndi-name="java:/ldapDS" pool-name="rhLdapDS" enabled="true">
                    <connection-url>jdbc:teiid:ldapVDB at mms://jdv.qa.a1.vary.redhat.com:31000;version=1</connection-url>
                    <driver>teiid-8.13.3-jdbc.jar</driver>
                    <pool>
                        <prefill>false</prefill>
                        <use-strict-min>false</use-strict-min>
                        <flush-strategy>FailingConnectionOnly</flush-strategy>
                    </pool>
                    <security>
                        <user-name>--</user-name>
                        <password>**</password>
                    </security>
                </datasource>
{code}



> Teiid datasource driver does not reconnect after socket is closed
> -----------------------------------------------------------------
>
>                 Key: TEIID-4696
>                 URL: https://issues.jboss.org/browse/TEIID-4696
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Driver
>    Affects Versions: 8.13.3
>         Environment: - Red Hat JBoss Enterprise Application Platform - Version 6.4.5.GA
> - Load Balancer
> - Red Hat JBoss Data Virtualization - Version 6.3.0
>            Reporter: Rafael Coutinho
>            Assignee: Steven Hawkins
>         Attachments: one_first_exceptions.txt, two_repeated_exceptions.txt
>
>
> Our setup has a JBoss app server with a datasource configured to query a virtual database deployend on a JDV server that is behind a load balancer.
> The load balancer drops any connection after 10 minutes. For some reason the datasource client driver does not fix the connection when the socket gets closed. So in any queries done after the socket is closed are breaking, they log that the socket is closed but it never re establishes the connection again.
> Attachment one has the first exception stack trace, attachment number two has the subsequent ones.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)