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

ASF GitHub Bot commented on ARTEMIS-1980:
-----------------------------------------

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2181

    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

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/activemq-artemis ARTEMIS-1980

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2181
    
----
commit a33e3536ee3f186a52d44517398cda4daff763de
Author: Francesco Nigro <nigro.fra@...>
Date:   2018-07-12T13:14:37Z

    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)

Reply via email to