You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/17 22:37:41 UTC
[jira] [Commented] (TRAFODION-2594) Trafodion logs the same message
twice in most of its log4j and log4cxx logs
[ https://issues.apache.org/jira/browse/TRAFODION-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971761#comment-15971761 ]
ASF GitHub Bot commented on TRAFODION-2594:
-------------------------------------------
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 <se...@esgyn.com>
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
----
> Trafodion logs the same message twice in most of its log4j and log4cxx logs
> ---------------------------------------------------------------------------
>
> Key: TRAFODION-2594
> URL: https://issues.apache.org/jira/browse/TRAFODION-2594
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-general
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> For an example the SSMP process logs as follows
> 2016-12-11 01:33:11,994, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666, Process Name: $ZSM000,,, An ssmp process is launched.
> 2016-12-11 01:33:11,994, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666, Process Name: $ZSM000,,, An ssmp process is launched.
> 2016-12-12 02:55:02,141, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666, Process Name: $ZSM000,,,Early reply to query started message from $Z000MQW:466 to attempt graceful cancel of query MXID11000027856212348271213304001000000000206U3333300_415_S1. Explain Sequence Number: 0 FILE: ../runtimestats/CancelBroker.cpp LINE: 149
> 2016-12-12 02:55:02,141, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666, Process Name: $ZSM000,,,Early reply to query started message from $Z000MQW:466 to attempt graceful cancel of query MXID11000027856212348271213304001000000000206U3333300_415_S1. Explain Sequence Number: 0 FILE: ../runtimestats/CancelBroker.cpp LINE: 149
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)