[
https://issues.apache.org/jira/browse/ARTEMIS-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292168#comment-16292168
]
ASF GitHub Bot commented on ARTEMIS-1541:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1691
@mtaylor I've performed the failover tests on other DBMS and it is working
as expected, but disabling the `ThreadLeakCheckRule` due to a "known" leak on
the Oracle thin driver - the uninterruptible/unstoppable/unbreakable
`oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser`
thread:
```
public void run() {
while(true) {
try {
BlockSource.ThreadedCachingBlockSource.BlockReleaser var1 = SOLE_INSTANCE;
synchronized(SOLE_INSTANCE) {
SOLE_INSTANCE.wait(300000L);
}
BlockSource.ThreadedCachingBlockSource.releaseFromAllSources();
} catch (Throwable var4) {
;
}
}
}
```
> 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)
