You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Anuradha Hegde (JIRA)" <ji...@apache.org> on 2015/10/06 17:52:26 UTC

[jira] [Commented] (TRAFODION-59) LP Blueprint: eventmanagement - Event Publication using log4cpp

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

Anuradha Hegde commented on TRAFODION-59:
-----------------------------------------

This blueprint can be closed as we were using log4cpp to publish events. With the move to Apache we have leveraged the use of log4cxx for publication of events


> LP Blueprint: eventmanagement - Event Publication using log4cpp
> ---------------------------------------------------------------
>
>                 Key: TRAFODION-59
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-59
>             Project: Apache Trafodion
>          Issue Type: New Feature
>            Reporter: Rao Kakarlamudi
>            Assignee: Tharak Capirala
>            Priority: Critical
>             Fix For: 1.0 (pre-incubation)
>
>
> In the Trafodion project there is now a shift to use log4cpp (Apache open source project) to log error/event messages across all the sub components. The current proposal is to develop a simple and general approach that uses log4cpp, which can be used by all Trafodion components with minimum code changes. Some of the SQL components are already using log4cpp in a limited way. The SQL team have developed some wrapper classes around log4cpp and some configuration files. The idea is to leverage this existing infrastructure and generalize it for sub components.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)