GitHub user selvaganesang opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1068

    [TRAFODION-2594] Trafodion logs the same message twice in most of its…

    … log4j and log4cxx logs
    
    [TRAFODION-2420] RMS enhancements
    [TRAFODION-2478] Memory monitor Thread enhancements
    
    a) Changed the configuration to have log4j.additive property set to false
    b) ScratchIOSize is initialized so that this counter doesn't show invalid
       value
    c) Cleaned up memory monitor concept and added code to log the memory 
monitoring
       counters to sccp log file every 5 minutes or when there is a pressure 
difference

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

    $ git pull https://github.com/selvaganesang/incubator-trafodion 
trafodion-2420_2

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

    https://github.com/apache/incubator-trafodion/pull/1068.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 #1068
    
----
commit a4df3302f5fdcbf8abd165fed8b0da48c2de132f
Author: selvaganesang <[email protected]>
Date:   2017-04-15T18:53:34Z

    [TRAFODION-2594] Trafodion logs the same message twice in most of its log4j 
and log4cxx logs
    [TRAFODION-2420] RMS enhancements
    [TRAFODION-2478] Memory monitor Thread enhancements
    
    a) Changed the configuration to have log4j.additive property set to false
    b) ScratchIOSize is initialized so that this counter doesn't show invalid
       value
    c) Cleaned up memory monitor concept and added code to log the memory 
monitoring
       counters to sccp log file every 5 minutes or when there is a pressure 
difference

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to