You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/03/28 15:55:00 UTC

[jira] [Commented] (ARTEMIS-1541) Make the JDBC Node Manager more resilient on failures

    [ https://issues.apache.org/jira/browse/ARTEMIS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417601#comment-16417601 ] 

ASF subversion and git services commented on ARTEMIS-1541:
----------------------------------------------------------

Commit f005da6dfdf4d51b244e360abdf1906f7d45670d in activemq-artemis's branch refs/heads/1.x from [~nigro.fra@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=f005da6 ]

ARTEMIS-1541 Make the JDBC Node Manager more resilient on failures

(cherry picked from commit 70b21725edae28b591b87bb4de0f51364e9cfd50)


> Make the JDBC Node Manager more resilient on failures
> -----------------------------------------------------
>
>                 Key: ARTEMIS-1541
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1541
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>
> The JDBC Node Manager isn't showing (at any level) errors on setup and hasn't any policy to fail or recover while executing certain critical operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)