[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 closed WFCORE-478.
--------------------------------
Resolution: Out of Date
This was fixed at some point likely with the of org.jboss.logmanager:log4j-jboss-logmanager:1.1.2.Final.
> 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.4.11#64026)
10 years, 7 months
[JBoss JIRA] (ELY-300) Absence of key-store-credential NPEs
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-300?page=com.atlassian.jira.plugin.sy... ]
David Lloyd reassigned ELY-300:
-------------------------------
Assignee: David Lloyd (was: Darran Lofthouse)
> Absence of key-store-credential NPEs
> ------------------------------------
>
> Key: ELY-300
> URL: https://issues.jboss.org/browse/ELY-300
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Kabir Khan
> Assignee: David Lloyd
> Fix For: 1.1.0.Alpha1
>
>
> Trying to parse
> {code}
> <authentication-client xmlns="urn:elytron:1.0">
> <key-stores>
> <key-store name="test" type="PasswordFile">
> <file name="keystore/xml-client-keystore-credential-test.keystore"/>
> <!--<key-store-credential key-store-name="test" alias="test-alias"/>-->
> </key-store>
> </key-stores>
> </authentication-client>
> {code}
> I end up with
> {code}
> java.lang.NullPointerException
> at org.wildfly.security.auth.client.ElytronXmlParser$AbstractKeyStoreFactory.create(ElytronXmlParser.java:1082)
> at org.wildfly.security.auth.client.ElytronXmlParser$AbstractKeyStoreFactory.create(ElytronXmlParser.java:1067)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$115(ElytronXmlParser.java:709)
> at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$4/1929600551.create(Unknown Source)
> at org.wildfly.security.auth.client.KeyStoreEntrySecurityFactory.create(KeyStoreEntrySecurityFactory.java:47)
> at org.wildfly.security.auth.client.KeyStoreEntrySecurityFactory.create(KeyStoreEntrySecurityFactory.java:30)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRuleType$106(ElytronXmlParser.java:425)
> at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$5/1053782781.create(Unknown Source)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRuleType$113(ElytronXmlParser.java:474)
> at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$6/2012232625.create(Unknown Source)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRulesType$88(ElytronXmlParser.java:242)
> at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$7/627150481.create(Unknown Source)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45)
> at org.wildfly.security.auth.client.XmlClientKeyStoreCredentialTest.testKeystoreCredential(XmlClientKeyStoreCredentialTest.java:110)
> {code}
> This appears to be because the passwordFactory is only instantiated when parsing the key-store-credential element
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5436) Lack of EmbeddedCacheManager.undefineConfiguration(String) can cause memory/classloader leaks
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5436?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved ISPN-5800 to WFLY-5436:
------------------------------------------
Project: WildFly (was: Infinispan)
Key: WFLY-5436 (was: ISPN-5800)
Workflow: GIT Pull Request workflow (was: GIT Pull Request with Triage workflow)
Component/s: Clustering
(was: Configuration)
Fix Version/s: (was: 8.0.0.Final)
(was: 8.0.0.Alpha2)
> Lack of EmbeddedCacheManager.undefineConfiguration(String) can cause memory/classloader leaks
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-5436
> URL: https://issues.jboss.org/browse/WFLY-5436
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Tristan Tarrant
> Priority: Critical
>
> EmbeddedCacheManager has defineConfiguration(...) methods for defining a new cache configuration, but has no equivalent "undefine" method. Consequently, once defined, a cache manager will retains a reference to the cache configuration object for the lifetime of the cache manager. While this is normally not a big deal, the configuration objects generated by WildFly contain references to the classloaders of foreign modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5436) Lack of EmbeddedCacheManager.undefineConfiguration(String) can cause memory/classloader leaks
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5436?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reassigned WFLY-5436:
----------------------------------
Assignee: Paul Ferraro (was: Tristan Tarrant)
> Lack of EmbeddedCacheManager.undefineConfiguration(String) can cause memory/classloader leaks
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-5436
> URL: https://issues.jboss.org/browse/WFLY-5436
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
>
> EmbeddedCacheManager has defineConfiguration(...) methods for defining a new cache configuration, but has no equivalent "undefine" method. Consequently, once defined, a cache manager will retains a reference to the cache configuration object for the lifetime of the cache manager. While this is normally not a big deal, the configuration objects generated by WildFly contain references to the classloaders of foreign modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JGRP-1966) Specify logger name for LogRecord in JDKLogImpl
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1966?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1966:
---------------------------
Fix Version/s: 3.6.6
> Specify logger name for LogRecord in JDKLogImpl
> -----------------------------------------------
>
> Key: JGRP-1966
> URL: https://issues.jboss.org/browse/JGRP-1966
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 3.6.6
> Reporter: George Zalizko
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.6.6
>
>
> I use Spring Boot with logback.
> For logging I have pattern:
> {code}%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} %C{30}:%L - %msg%n{code}
> And in console I see:
> {code}
> 16:19:32.062 [OOB-1,yphis-cluster-web,George-THINKPAD-35404] WARN unknown.jul.logger org.jgroups.logging.JDKLogImpl:49 - JGRP000010: packet from 192.168.50.123:45588 has different version (3.2.8) than ours (3.6.6); packet is discarded{code}
> This happens because LogRecord created in org.jgroups.logging.JDKLogImpl doesn't have loggerName and when org.slf4j.bridge.SLF4JBridgeHandler make org.slf4j.Logger from java.util.logging.LogRecord he sets logger name as org.slf4j.bridge.SLF4JBridgeHandler#UNKNOWN_LOGGER_NAME that's "unknown.jul.logger"
> Actually I don't know is it done specially or not, but I can't find any comments/solutions for that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months