[ https://issues.apache.org/jira/browse/ARTEMIS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632212#comment-16632212 ]
ASF GitHub Bot commented on ARTEMIS-1980: ----------------------------------------- Github user clebertsuconic commented on a diff in the pull request: https://github.com/apache/activemq-artemis/pull/2181#discussion_r221341393 --- Diff: artemis-jdbc-store/src/main/java/org/apache/activemq/artemis/jdbc/store/drivers/AbstractJDBCDriver.java --- @@ -227,7 +227,11 @@ private void createTableIfNotExists(String tableName, String... sqls) throws SQL } } } catch (SQLException e) { - logger.warn(JDBCUtils.appendSQLExceptionDetails(new StringBuilder("Can't verify the initialization of table ").append(tableName).append(" due to:"), e, sqlProvider.getCountJournalRecordsSQL())); + if (logger.isDebugEnabled()) { --- End diff -- I feel really wrong on if (logger.isDebug()) logger.debug(...); else logger.info(...); it's either always info, or always debug... > 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)