[ https://issues.apache.org/jira/browse/ARTEMIS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673148#comment-16673148 ]
ASF subversion and git services commented on ARTEMIS-1980: ---------------------------------------------------------- Commit 46542fb230a31d621be9cdf4140df998d6dc3903 in activemq-artemis's branch refs/heads/master from [~nigro....@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=46542fb ] ARTEMIS-1980 Warn on failed check of table existence should be info DB2 metadata checks should erroneously report stale table existence on not existing/just deleted table, making the subsequent warning logs of failed SELECT COUNT useless and scaring: should be better to let them lowered to INFO level > Warn on failed check of table existence should be info > ------------------------------------------------------ > > Key: ARTEMIS-1980 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1980 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker > Affects Versions: 2.6.2 > Reporter: Francesco Nigro > Assignee: Francesco Nigro > Priority: Trivial > Fix For: 2.7.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > DB2 metadata checks should erroneously report stale table existence on > not existing/just deleted table, making the subsequent warning logs of failed > SELECT COUNT useless and scaring: should be better to let them lowered to > INFO level, avoiding users log reporting tools (if any) to react to an > expected behaviour. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)