December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-479) The testFormats() tests in the HandlerOperationsTestCase needs to ensure colors are being used

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-479?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-1860 to WFCORE-479: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-479 (was: WFLY-1860) Component/s: Logging (was: Logging) > The testFormats() tests in the HandlerOperationsTestCase needs to ensure colors are being used > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-479 > URL: https://issues.jboss.org/browse/WFCORE-479 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > In environments like Windows colored log output is not turned on by default. The test needs to take this into account and not assume that colored output will be printed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-478) log4j ConsoleAppender won't display messages with per-deployment logging

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-478?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-2012 to WFCORE-478: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-478 (was: WFLY-2012) Component/s: Logging (was: Logging) > log4j ConsoleAppender won't display messages with per-deployment logging > ------------------------------------------------------------------------ > > Key: WFCORE-478 > URL: https://issues.jboss.org/browse/WFCORE-478 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Add the following log4j.properties file to a deployment and try to log. > {code} > # Root logger option > log4j.rootLogger=INFO, stdout > # Direct log messages to stdout > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > log4j.appender.stdout.Target=System.out > log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2309) Fix description resolvers for logging extension

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2309?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-2309. ------------------------------- Resolution: Out of Date This was fixed upstream > Fix description resolvers for logging extension > ----------------------------------------------- > > Key: WFLY-2309 > URL: https://issues.jboss.org/browse/WFLY-2309 > Project: WildFly > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The logging extensions description resolver is a mess. In some cases doesn't allow the same attribute name to be used resources and get a different description. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-477) RootSubsystemOperationsTestCase fails if log directory wasn't properly cleaned

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-477?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-2395 to WFCORE-477: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-477 (was: WFLY-2395) Component/s: Logging (was: Logging) > RootSubsystemOperationsTestCase fails if log directory wasn't properly cleaned > ------------------------------------------------------------------------------ > > Key: WFCORE-477 > URL: https://issues.jboss.org/browse/WFCORE-477 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Some test appears to not be cleaning up the {{target/logs}} directory which causes the tests to fail. While tests should be cleaning up after themselves, the test in the {{RootSubsystemOperationsTestCase}} should also not look for empty directories, but look for the files that _shouldn't_ be there. > Files left behind: > {code} > [root@build01 logging]# ls -l target/logs/ > total 0 > -rw-r--r-- 1 root root 0 Oct 28 23:00 another.log > -rw-r--r-- 1 root root 0 Oct 28 23:00 anotherProfile.log > -rw-r--r-- 1 root root 0 Oct 28 23:00 fileHandler.log > -rw-r--r-- 1 root root 0 Oct 28 23:00 profileFileHandler.log > -rw-r--r-- 1 root root 0 Oct 28 23:00 server.log > -rw-r--r-- 1 root root 0 Oct 28 23:00 sizeLogger.log > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2826) The list-log-files operation should have an option for sorting the results

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2826?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-2826. ------------------------------- Resolution: Out of Date Operations has been deprecated and the {{subsystem=logging/log-file=*}} resources are preferred. > The list-log-files operation should have an option for sorting the results > -------------------------------------------------------------------------- > > Key: WFLY-2826 > URL: https://issues.jboss.org/browse/WFLY-2826 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Currently the {{list-log-files}} operation sorts the results by the file name. The output includes the size and the last modified date. The results should be sortable by these fields too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-476) Redhat/Debian script problem when deleting Console Handler

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-476?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-3397 to WFCORE-476: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-476 (was: WFLY-3397) Affects Version/s: (was: 8.1.0.CR2) Component/s: Scripts (was: Scripts) > Redhat/Debian script problem when deleting Console Handler > ---------------------------------------------------------- > > Key: WFCORE-476 > URL: https://issues.jboss.org/browse/WFCORE-476 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marcial Atiénzar Navarro > Assignee: James Perkins > Priority: Minor > > The scripts to start wildfly as service on redhat/debian use this code: > {code} > until [ $count -gt $STARTUP_WAIT ] > do > grep 'JBAS015874:' "$JBOSS_CONSOLE_LOG" > /dev/null > if [ $? -eq 0 ] ; then > launched=1 > break > fi > sleep 1 > count=$((count + 1)); > done > {code} > But if you have delete console handler in production enviroment, and increase the startup_wait because you have more applications deployed on server, it takes to start all the time specified on STARTUP_WAIT -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-475) Properties for custom-handlers and custom-formatters should allow for a constructor option

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-475?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-3544 to WFCORE-475: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-475 (was: WFLY-3544) Component/s: Logging (was: Logging) > Properties for custom-handlers and custom-formatters should allow for a constructor option > ------------------------------------------------------------------------------------------ > > Key: WFCORE-475 > URL: https://issues.jboss.org/browse/WFCORE-475 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Currently for a {{custom-handler}} or {{custom-formatter}} the {{properties}} attribute only uses setter methods. There should be a way to specify a property should be used as a constructor property. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-474) Custom formatter property changes not written to, but overriden by logging.properties

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-474?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-3931 to WFCORE-474: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-474 (was: WFLY-3931) Affects Version/s: (was: 8.1.0.Final) Component/s: Logging (was: Logging) > Custom formatter property changes not written to, but overriden by logging.properties > ------------------------------------------------------------------------------------- > > Key: WFCORE-474 > URL: https://issues.jboss.org/browse/WFCORE-474 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Wildfly 8.1.0.Final > Reporter: Vsevolod Golovanov > Assignee: James Perkins > Attachments: standalone.xml > > > When you first add custom formatter with properties to standalone.xml, on server start property values get correctly resolved and written to logging.properties. > If you change property values in standalone.xml of an existing custom formatter, that was flushed to logging.properties before, then on the next server start new values don't get written to logging.properties and formatter instance gets the old values from logging.properties. > For properties with static values that are defined in standalone.xml there is a workaround: change the custom formatter name each time you change a property value. > But with more dynamic properties, e.g. that rely on system properties, it's not so simple... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4032) Standalone.bat not support log dir with spaces in path (jboss.server.log.dir)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4032?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-4032. ------------------------------- Resolution: Out of Date This should be working upstream > Standalone.bat not support log dir with spaces in path (jboss.server.log.dir) > ----------------------------------------------------------------------------- > > Key: WFLY-4032 > URL: https://issues.jboss.org/browse/WFLY-4032 > Project: WildFly > Issue Type: Bug > Components: Batch, Logging, Scripts > Affects Versions: 8.1.0.Final > Environment: Windows 7 > Reporter: Duc Quoc > Assignee: James Perkins > Priority: Minor > > I tried to specify a custom log folder for WildFly, by overriding property jboss.server.log.dir > https://docs.jboss.org/author/display/WFLY8/Command+line+parameters > But it only works for folder without space in path. The ones with space when used with "jboss.server.log.dir" will prevent wildfly from starting. > Working: > C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat > C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Windows" > Not working (server can not start): > C:\>start C:\wildfly-8.1.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" > (More info: > JBoss AS 7.1 works: > C:\> start C:\jboss-as-7.1.1.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" > JBoss EAP 6 and WildFly 8.0 not working either: > C:\> start C:\jboss-eap-6.2\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" > C:\> start C:\wildfly-8.0.0.Final\bin\standalone.bat -Djboss.server.log.dir="C:\Program Files" > Aready tried setting jboss.server.log.dir="C:\Program Files" in JAVA_OPTS but did not work either. Should have been fixed in WFLY-1358 or WFLY-2348. > ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3397) Redhat/Debian script problem when deleting Console Handler

by Jorge Solorzano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3397?page=com.atlassian.jira.plugin.... ] Jorge Solorzano commented on WFLY-3397: --------------------------------------- In that case I can make the check to the process status and not verify the log output.... but this way it will return OK right away even if there is an error in the start, for example problems of permissions, etc. Since the process is really started but not fully operational. BTW is a bad practice to remove the console handler since it makes difficult to diagnose possible problems on startup. > Redhat/Debian script problem when deleting Console Handler > ---------------------------------------------------------- > > Key: WFLY-3397 > URL: https://issues.jboss.org/browse/WFLY-3397 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.1.0.CR2 > Reporter: Marcial Atiénzar Navarro > Assignee: James Perkins > Priority: Minor > > The scripts to start wildfly as service on redhat/debian use this code: > {code} > until [ $count -gt $STARTUP_WAIT ] > do > grep 'JBAS015874:' "$JBOSS_CONSOLE_LOG" > /dev/null > if [ $? -eq 0 ] ; then > launched=1 > break > fi > sleep 1 > count=$((count + 1)); > done > {code} > But if you have delete console handler in production enviroment, and increase the startup_wait because you have more applications deployed on server, it takes to start all the time specified on STARTUP_WAIT -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014