Cargo

Incorrect log4j logging levels are used in JBoss

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.0.3
  • Component/s: JBoss
  • Labels:
    None
  • Environment:
    n/a
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

The values for the cargo.logging property is inserted in the jboss log4j file. As those values are not correct log4j values ("low", "medium", or "high"), this makes JBoss/log4j spit out an error messages. Also, maybe more importantly, logging is set to debug which provides for a very verbose log.
We need to translate the cargo.logging values into correct log4j values.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. CARGO-585 Maven/Cargo/JBoss problem with verbose, unconfigurable logging

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Improvement - An improvement or enhancement to an existing feature or task. CARGO-823 Set properties for JBoss configuration changes instead of using cargo-specific config files

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
Anders Hammar added a comment -

This was fixed when fixing CARGO-823.

Show
Anders Hammar added a comment - This was fixed when fixing CARGO-823 .

People

  • Assignee:
    Anders Hammar
    Reporter:
    Anders Hammar
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: