[GitHub] activemq-artemis pull request #1213: resilience JDBC

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis pull request #1213: resilience JDBC

asfgit
GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1213

    resilience JDBC

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/clebertsuconic/activemq-artemis jdbc-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1213.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1213
   
----
commit d9fb39b30de8501e343e18266b099ba49eca9f94
Author: Martyn Taylor <[hidden email]>
Date:   2017-04-17T09:40:26Z

    ARTEMIS-1115 Call CriticalIOListener on JDBC Error

commit 727eb677d08c39d6de73b57f0e7f0a3fa6eb8e3c
Author: Clebert Suconic <[hidden email]>
Date:   2017-04-18T18:36:25Z

    ARTEMIS-1115 Traces and tests on JDBC Persistence

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] activemq-artemis pull request #1213: resilience JDBC

asfgit
Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1213


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...