October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-124) Add marker support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-124: --------------------------------- Priority: Optional (was: Major) > Add marker support > ------------------ > > Key: LOGMGR-124 > URL: https://issues.jboss.org/browse/LOGMGR-124 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.2.Final > Reporter: Rob Heine > Priority: Optional > > The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-92) [tests] LoggerTests.testResourceBundle fails on german windows

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-92?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-92: ----------------------------------- Assignee: (was: James Perkins) > [tests] LoggerTests.testResourceBundle fails on german windows > -------------------------------------------------------------- > > Key: LOGMGR-92 > URL: https://issues.jboss.org/browse/LOGMGR-92 > Project: JBoss Log Manager > Issue Type: Bug > Affects Versions: 1.3.2.Final, 2.0.0.Beta1 > Environment: maven 3.0.2 on Win7x64 cygwin > Reporter: Bernd Eckenfels > Priority: Minor > Labels: i18n > > When I run "mvn test" for the logmanager build (various branches) on german Win7 it fails with > Tests run: 42, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.834 sec <<< FAILURE! > Results: Failed tests: testResourceBundle(org.jboss.logmanager.LoggerTests): Can't find org.jboss.logmanager.LoggerTests bundle > Tests run:42 ,Failures:1, Errors:0,Skipped:0 > ava.util.MissingResourceException: Can't find org.jboss.logmanager.LoggerTests bundle > at java.util.logging.Logger.setupResourceInfo(Logger.java:1335) > at java.util.logging.Logger.getLogger(Logger.java:335) > at org.jboss.logmanager.Logger.getLogger(Logger.java:75) > at org.jboss.logmanager.LoggerTests.testResourceBundle(LoggerTests.java:149) > It helps to copy src/test/resources/org/jboss/logmanager/LoggerTests_en.properties to LoggerTests.properties, however strangely enough it does not help to manually specify user.language=en in the surefire configuration. The test should at least skip itself if the locale is not specified correctly (or ship locale independend translation). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-97) AS6 org.jboss.logmanager.handlers.SizeRotatingFileHandler bug

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-97?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-97: ----------------------------------- Assignee: (was: James Perkins) > AS6 org.jboss.logmanager.handlers.SizeRotatingFileHandler bug > ------------------------------------------------------------- > > Key: LOGMGR-97 > URL: https://issues.jboss.org/browse/LOGMGR-97 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: Ivan Chupakhin > > method preWrite : > for (int i = maxBackupIndex - 1; i > 1; i--) > { > new File(file.getAbsolutePath() + "." + i).renameTo(new c File(file.getAbsolutePath() + "." + (i - 1))); > } > Logical error while renaming log files, the arguments of renameTo function are passed in the wrong order. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-82) PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-82?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-82: ----------------------------------- Assignee: (was: James Perkins) > PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy > -------------------------------------------------------------------- > > Key: LOGMGR-82 > URL: https://issues.jboss.org/browse/LOGMGR-82 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > > The rotation tests seem to fail at random days and times. The test {{testPeriodicAndSizeRotate}} needs to be looked at before re-enabling it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-115) Writing the configuration file should handle properties with null values

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-115?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-115: ------------------------------------ Assignee: (was: James Perkins) > Writing the configuration file should handle properties with null values > ------------------------------------------------------------------------ > > Key: LOGMGR-115 > URL: https://issues.jboss.org/browse/LOGMGR-115 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Priority: Minor > > Currently in the configuration API if a property is set to {{null}} an NPE occurs during the write and is swallowed. The idea was the {{removeProperty()}} should be used in the API. We should though check for {{null}} values and either not write the value or leave the value blank and have the reader for the configuration assume a value of 0 length is {{null}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-57) Log files cleanup for periodic-rotating-file-handler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-57?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-57: ----------------------------------- Assignee: (was: James Perkins) > Log files cleanup for periodic-rotating-file-handler > ---------------------------------------------------- > > Key: LOGMGR-57 > URL: https://issues.jboss.org/browse/LOGMGR-57 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: Razvan Popa > Priority: Minor > > Hi, > It would be useful for the periodic-rotating-file-handler to have a "max-backup-index" attribute to allow the removal of older files like in the size-rotating-file-handler. > It would also be nice to have something like "archive-older-than" and "delete-older-than" to also keep some older files archived for a while. > Regards, > Razvan -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-105) Allow encoding to be overridden in a SyslogHandler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-105?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-105: ------------------------------------ Assignee: (was: James Perkins) > Allow encoding to be overridden in a SyslogHandler > -------------------------------------------------- > > Key: LOGMGR-105 > URL: https://issues.jboss.org/browse/LOGMGR-105 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > > Currently the encoding for a {{SyslogHandler}} is ignored expect for printing the UTF-8 byte order mark. The encoding should probably be allowed to be changed so that syslog messages can be sent with other encodings. > While the RFC-5424 documentation does indicate UTF-8 should be used, it does allow for other encoding types. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-80) Support Logback similar to how Log4J is supported

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-80?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-80: ----------------------------------- Assignee: (was: James Perkins) > Support Logback similar to how Log4J is supported > ------------------------------------------------- > > Key: LOGMGR-80 > URL: https://issues.jboss.org/browse/LOGMGR-80 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: Kyle Lape > > It would be nice to have support for Logback similar to how we support Log4J. Specifically, provide a modified version of Logback with customizations that account for the classloading behavior of Wildfly/JBoss Modules, thus removing the need to include logback libraries in deployments. > It could be argued that there is no need for this because Logback does not provide a logging facade API and that anyone that migrates to Wildfly should migrate their {{logback.xml}} to something JBoss already supports. While that's a valid point, any help that could be provided to folks migrating to Wildfly would be appreciated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-98) Disable UTF-8 BOM in syslog handler when encoding is undefined

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-98?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-98: ----------------------------------- Assignee: (was: James Perkins) > Disable UTF-8 BOM in syslog handler when encoding is undefined > -------------------------------------------------------------- > > Key: LOGMGR-98 > URL: https://issues.jboss.org/browse/LOGMGR-98 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: Kyle Lape > > Section 6.4 MSG: http://tools.ietf.org/html/rfc5424#section-6.4 > bq. If a syslog application encodes MSG in UTF-8, the string MUST start with the Unicode byte order mask (BOM), which for UTF-8 is ABNF %xEF.BB.BF. The syslog application MUST encode in the "shortest form" and MAY use any valid UTF-8 sequence. > While we want to conform to the spec, it is desirable to not include the BOM in some practical applications, e.g. rsyslog does not strip the BOM, and sometimes it would be easier to be able to configure JBoss to not include the BOM than to configure rsyslog to drop it. > Perhaps we can not include the BOM is the encoding is undefined for the {{SyslogHandler}}, but do include it if the {{encoding}} is explicitly set to {{UTF-8}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-121) Support Log4J2 API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-121?page=com.atlassian.jira.plugin... ] James Perkins reassigned LOGMGR-121: ------------------------------------ Assignee: (was: James Perkins) > Support Log4J2 API > ------------------ > > Key: LOGMGR-121 > URL: https://issues.jboss.org/browse/LOGMGR-121 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Livingston > > The API of Log4j 1.2 is supported by https://github.com/jboss-logging/log4j-jboss-logmanager, to bridge that API to our logging implementation. > It would be useful to have an equivalent bridge for the Log4J2 API, which may be easier than for 1.2 since the API is split from the implementation. > It may be possible to http://logging.apache.org/log4j/2.x/log4j-to-slf4j/index.html as a work-around, so Log4J2 bridges to SLF4J, which is bridged to JBoss LogManager -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2015