[
https://issues.apache.org/jira/browse/ARTEMIS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292237#comment-16292237
]
ASF GitHub Bot commented on ARTEMIS-1541:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1691
@mtaylor
> and the thread does not cause interference with other tests
That's the part I'm sure of it: it seems that only a SIGKILL can close a
process that has any of these threads running-
> Which systems did you run the tests against?
Do you mean which versions of which DBMS?
> It would be good to have this set up in the CI env
Considering that I'm not sure that is possible to kill gently the Oracle
one, how do you propose to do that?
eg The Oracle thin driver is not on maven AFAIK
> 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
>
> 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
(v6.4.14#64029)
