December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-871: -------------------------------------------------- Jimmy Wilson <jawilson(a)redhat.com> changed the Status of [bug 1170767|https://bugzilla.redhat.com/show_bug.cgi?id=1170767] from NEW to CLOSED > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-483) Allow hooking into logging subsystem through Management API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-483?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-1048 to WFCORE-483: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-483 (was: WFLY-1048) Component/s: Logging (was: Logging) > Allow hooking into logging subsystem through Management API > ----------------------------------------------------------- > > Key: WFCORE-483 > URL: https://issues.jboss.org/browse/WFCORE-483 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: Ondrej Zizka > Assignee: James Perkins > Labels: logging > > Provide a way to poll log messages through the management API. > Could be then used in the AS console. Some kind of detached window, or perhaps tab, with log, perhaps pushed through Servlet 3.2's onDataAvailable() ... > Note that this is different from AS7-2213, which needs AS to keep some history. This doesn't. > BTW, JBDS gets the logs through SSH, because the AS may fail booting before anything is able to hook in like this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-1037 to WFCORE-482: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-482 (was: WFLY-1037) Component/s: Logging (was: Logging) > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.jboss.org/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Optional > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-481) Logging async-handler improvement - report number dropped logs

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-481?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-4178 to WFCORE-481: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-481 (was: WFLY-4178) Affects Version/s: (was: 8.0.0.Final) Component/s: Logging (was: Logging) > Logging async-handler improvement - report number dropped logs > -------------------------------------------------------------- > > Key: WFCORE-481 > URL: https://issues.jboss.org/browse/WFCORE-481 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Todd Sandor > Assignee: James Perkins > > The functional requirement is to know when logs are discarded and the number of logs discarded. > When using a async-handler such as the one below, we do not know if/when logs are discarded, thousands could be dropped and we do not know it. > <async-handler name="ASYNC"> > <queue-length value="300000"/> > <overflow-action value="discard"/> > <subhandlers> > <handler name="FILE"/> > </subhandlers> > </async-handler> > Potential solution/suggestion: > Add a new property, call it max-discard-logs, with a default value of 1 - uses existing behavior when = 1 (when queue full, drop any new log). > When > 1 and queue is full, at least max-discard-logs logs are removed from the queue and display a log indicating the queue is full an N logs were dropped. > <async-handler name="ASYNC"> > <queue-length value="300000"/> > <overflow-action value="discard"/> > <max-discard-logs value="1000"/> > <subhandlers> > <handler name="FILE"/> > </subhandlers> > </async-handler> > Depending upon the type of queue being used in the implementation, this could be a very simple change. > e.g > https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/BlockingQu... > int drainTo(Collection<? super E> c, int maxElements) > Removes at most the given number of available elements from this queue and adds them to the given collection. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-997) standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-997?page=com.atlassian.jira.plugin.s... ] James Perkins closed WFLY-997. ------------------------------ Resolution: Out of Date Should be fixed upstream > standalone.sh / domain.sh does not support overriding jboss.server.base.dir, log and config dir in CYGWIN > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-997 > URL: https://issues.jboss.org/browse/WFLY-997 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Tom Fonteyne > Assignee: James Perkins > Priority: Minor > > There is a check on linux, so a cygwin system will not execute this block: > if $linux; then > # consolidate the server and command line opts > CONSOLIDATED_OPTS="$JAVA_OPTS $SERVER_OPTS" > # process the standalone options > for var in $CONSOLIDATED_OPTS > do > case $var in > -Djboss.server.base.dir=*) > JBOSS_BASE_DIR=`readlink -m ${var#*=}` > ... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-480) Create more/better testing for custom logging handlers

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-480?page=com.atlassian.jira.plugin... ] James Perkins moved WFLY-1579 to WFCORE-480: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-480 (was: WFLY-1579) Component/s: Logging (was: Logging) > Create more/better testing for custom logging handlers > ------------------------------------------------------ > > Key: WFCORE-480 > URL: https://issues.jboss.org/browse/WFCORE-480 > Project: WildFly Core > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Custom handlers cannot be test in normal subsystem tests as they require a JBoss Modules class loader. A way to either launch surfire with JBoss Modules looked at or more and better ARQ tests need to be written. There have been several issues specifically around log4j appenders as custom handlers. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[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)

11 years, 7 months

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)

11 years, 7 months

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)

11 years, 7 months

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)

11 years, 7 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 December 2014