Petals SE XSLT

Remove process related information from the INFO log

Details

  • Type: Improvement Request Improvement Request
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 2.3.2
  • Fix Version/s: 2.4
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Each time a transformation is processed we got stuff like this in the Petals ESB console :

    [Petals.Container.Components.petals-se-xslt]-INFO 2010-07-30 10:23:41,749 Process the transformation

    Since this information is not relevant at INFO level, it may be preferable to change the logger level for this line to FINE / FINEST.

    Show
    Each time a transformation is processed we got stuff like this in the Petals ESB console : [Petals.Container.Components.petals-se-xslt]-INFO 2010-07-30 10:23:41,749 Process the transformation Since this information is not relevant at INFO level, it may be preferable to change the logger level for this line to FINE / FINEST.
  • Environment:
    PetalsESB 3.1
    Petals-SE-XSLT 2.3.2

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Roland Naudin added a comment - Fri, 30 Jul 2010 - 10:36:50 +0200

The logs at INFO level must be audit logs.
It means that they must indicate what event happends in the bus.
This trace is relevant at INFO level, but must contains the ExchangeID and the correlationID if defined.
If you do not want that kind of trace, change the log trace level at warning in the component.

Show
Roland Naudin added a comment - Fri, 30 Jul 2010 - 10:36:50 +0200 The logs at INFO level must be audit logs. It means that they must indicate what event happends in the bus. This trace is relevant at INFO level, but must contains the ExchangeID and the correlationID if defined. If you do not want that kind of trace, change the log trace level at warning in the component.
Hide
Permalink
Vincent Zurczak added a comment - Fri, 30 Jul 2010 - 10:51:54 +0200

I guess this is still the trunk version from last week.
Logging has been updated in the XSLT component since then.

For every processed exchange, the following elements are logged at the INFO level:
+ An exchange was received.
+ The request was validated, the transformation is about to start.
+ The exchange was successfully processed.
+ The exchange processing encountered a problem.

Each log entry for these elements (as well as for all of the JBI listener) starts with the exchange ID.
Logging rules for components are defined on this page: http://doc.petalslink.com/display/petalsesb/Advanced+topics+and+guidelines

Show
Vincent Zurczak added a comment - Fri, 30 Jul 2010 - 10:51:54 +0200 I guess this is still the trunk version from last week. Logging has been updated in the XSLT component since then. For every processed exchange, the following elements are logged at the INFO level: + An exchange was received. + The request was validated, the transformation is about to start. + The exchange was successfully processed. + The exchange processing encountered a problem. Each log entry for these elements (as well as for all of the JBI listener) starts with the exchange ID. Logging rules for components are defined on this page: http://doc.petalslink.com/display/petalsesb/Advanced+topics+and+guidelines

People

Dates

  • Created:
    Fri, 30 Jul 2010 - 10:29:25 +0200
    Updated:
    Fri, 30 Jul 2010 - 10:51:54 +0200
    Resolved:
    Fri, 30 Jul 2010 - 10:36:50 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.