May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-10796: ----------------------------- Description: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. was: Following warning is shown in log upon server start: {code} 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. {code} Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. > Warning about JSF version 'NONE' is shown in logs > -------------------------------------------------- > > Key: WFLY-10796 > URL: https://issues.jboss.org/browse/WFLY-10796 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > > Following warning is shown in log upon server start: > {code} > 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead. > {code} > Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

4 days, 9 hours

2
1
0 / 0

[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-776: ------------------------------------ Assignee: Darran Lofthouse > Eliminate reference to "slot" from module configurations > -------------------------------------------------------- > > Key: ELY-776 > URL: https://issues.jboss.org/browse/ELY-776 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

4 days, 9 hours

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

5 months

3
10
0 / 0

[JBoss JIRA] (WFLY-11109) Fix PatterFormatter documentation for host name pattern

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11109?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11109: --------------------------------- Description: Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the first segment of the host. The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: {code:title=Current Output} org {code} {code:title=Expected Output} developer {code} was: Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the last segment of the host. The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: {code:title=Current Output} org {code} {code:title=Expected Output} developer {code} > Fix PatterFormatter documentation for host name pattern > ------------------------------------------------------- > > Key: WFLY-11109 > URL: https://issues.jboss.org/browse/WFLY-11109 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the first segment of the host. > The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: > {code:title=Current Output} > org > {code} > {code:title=Expected Output} > developer > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11109) Fix PatterFormatter documentation for host name pattern

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11109?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-11109: --------------------------------- Description: Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the last segment of the host. The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: {code:title=Current Output} org {code} {code:title=Expected Output} developer {code} was: Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the first segment of the host. The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: {code:title=Current Output} org {code} {code:title=Expected Output} developer {code} > Fix PatterFormatter documentation for host name pattern > ------------------------------------------------------- > > Key: WFLY-11109 > URL: https://issues.jboss.org/browse/WFLY-11109 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently the short host name pattern, {{%h}}, is documented as allowing the a precision argument to be added. This should not be allowed and the short host should only be the last segment of the host. > The qualified host name pattern, {{%H}}, indicates the precision is done left to right just like a log category or class name. However in general a host name is the opposite direction and thus should be segmented from right to left instead. For example given the host name {{developer.jboss.org}} and a pattern of {{%H\{1\}}}: > {code:title=Current Output} > org > {code} > {code:title=Expected Output} > developer > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4364) Allow management audit logging to write JSON log messages to stdout

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4364?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-4364 at 5/31/19 4:56 PM: ---------------------------------------------------------------- Looking more at the data it's going to have to be fully restructured. The data looks like an object. It's probably going to have to look more like: {code} { "timestamp" : "2019-03-08 13:29:49" "type" : "core", "r/o" : false, "booting" : false, "version" : "8.0.1.CR1-SNAPSHOT", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "localhost/127.0.0.1", "success" : true, "opAddress" : "/subsystem=logging/json-formatter=json", "op" : "remove", "caller-type" : "user", "access-mechanism" : "NATIVE" } {code} Note we need to determine what values can end up in the {{operation-headers}} object. was (Author: jamezp): Looking more at the data it's going to have to be fully restructured. The date looks like an object. It's probably going to have to look more like: {code} { "timestamp" : "2019-03-08 13:29:49" "type" : "core", "r/o" : false, "booting" : false, "version" : "8.0.1.CR1-SNAPSHOT", "user" : "$local", "domainUUID" : null, "access" : "NATIVE", "remote-address" : "localhost/127.0.0.1", "success" : true, "opAddress" : "/subsystem=logging/json-formatter=json", "op" : "remove", "caller-type" : "user", "access-mechanism" : "NATIVE" } {code} Note we need to determine what values can end up in the {{operation-headers}} object. > Allow management audit logging to write JSON log messages to stdout > ------------------------------------------------------------------- > > Key: WFCORE-4364 > URL: https://issues.jboss.org/browse/WFCORE-4364 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging, Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators. > Example Output: > {code} > 2019-03-08 13:29:49 - { > "type" : "core", > "r/o" : false, > "booting" : false, > "version" : "8.0.1.CR1-SNAPSHOT", > "user" : "$local", > "domainUUID" : null, > "access" : "NATIVE", > "remote-address" : "localhost/127.0.0.1", > "success" : true, > "ops" : [{ > "address" : [ > { > "subsystem" : "logging" > }, > { > "json-formatter" : "json" > } > ], > "operation" : "remove", > "operation-headers" : { > "caller-type" : "user", > "access-mechanism" : "NATIVE" > } > }] > } > {code} > Note for a log aggregator the complex {{ops}} attribute can be an issue. We may need to find a better way to log that. If possibly maybe convert it into a CLI command. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4386) Unable to start WF with JDK11 and GC log enabled with space in folder name

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4386?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4386: --------------------------------------- In the PR https://github.com/wildfly/wildfly-core/pull/3797 I added some tests for different directories and the addition of tests which enable GC logging. While doing this I noticed that with Java 11 there were issues if the path contained a space. This may be related to https://bugs.openjdk.java.net/browse/JDK-8215398, however it seemed to work fine with the workaround assuming the path did not contain a space. Nothing I did seemed to be able to get around this issue. I'm not sure if it's something we can fix or not, but someone with a better knowledge of PowerShell may know a workaround. > Unable to start WF with JDK11 and GC log enabled with space in folder name > -------------------------------------------------------------------------- > > Key: WFCORE-4386 > URL: https://issues.jboss.org/browse/WFCORE-4386 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecky > Assignee: James Perkins > Priority: Major > > Unable to start WF with JDK11 and GC log enabled with space in folder name > "w f/bin/standalone.ps1" > Log: > {noformat} > [0.005s][error][logging] Missing terminating quote in -Xlog option 'file="C:\Users\Administrator\playground\w' > Invalid -Xlog option '-Xlog:gc*:file="C:\Users\Administrator\playground\w', see error log for details. > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {noformat} > The issue is caused by [this line of common.ps1 file|https://github.com/wildfly/wildfly-core/blob/master/core-feature-pac...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-201) Test Issue - please ignore

by Jason Brock (Jira)

[ https://issues.jboss.org/browse/JBEE-201?page=com.atlassian.jira.plugin.s... ] Jason Brock closed JBEE-201. ---------------------------- Resolution: Done > Test Issue - please ignore > -------------------------- > > Key: JBEE-201 > URL: https://issues.jboss.org/browse/JBEE-201 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Reporter: Jason Brock > Assignee: Jason Brock > Priority: Major > > Test issue please ignore > Security sensitive checkbox only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4089) EvaluatedExpression not well resolved with JIT during race

by vincent palau (Jira)

[ https://issues.jboss.org/browse/DROOLS-4089?page=com.atlassian.jira.plugi... ] vincent palau commented on DROOLS-4089: --------------------------------------- Oh yes, Great news :D I'm not sure about your release cycles. At each Sprint? When it will be available on the maven repo? Thanks a lot for this quick fix! > EvaluatedExpression not well resolved with JIT during race > ------------------------------------------------------------ > > Key: DROOLS-4089 > URL: https://issues.jboss.org/browse/DROOLS-4089 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.20.0.Final, 7.22.0.Final > Reporter: vincent palau > Assignee: Mario Fusco > Priority: Major > Attachments: debugging-1.png > > > We recently moved from Drools 7.9.0 to 7.20. > Some errors started appearing in ours tests when calling static methods in LHS drools. > This started happening when all tests were run simultaneously. > It seems the mvel JIT compiler kicks in and it incorrectly evaluates the property name: > A simple call to {noformat}ValidationUtils.isNullOrEmpty(interestedPartyNumber){noformat} ends up with this kind of error: > {noformat} > "java.lang.RuntimeException: Unknown property 'nullOrEmpty' on class tech.stage.utils.cwr.model.PublisherRecord" > {noformat} > Debugging info: > Related source-code: https://github.com/kiegroup/drools/blob/7.20.0.Final/drools-core/src/main... > !debugging-1.png|full! > 1) is the current evaluated property > 2) Should be the right property of WriterRecord > 3) Perhaps the expression which should be executed instead of invocations.get(0) > We fixed that somehow disabling JIT with {noformat}ConstraintJittingThresholdOption{noformat} > Is there any chance to this bug fixed? > Do you need more info? > Thanks in advance for your support. > {panel:title=Reproducer} > https://github.com/vp-stage/evaluatedexpressionandjit > {panel} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-201) Test Issue - please ignore

by Jason Brock (Jira)

[ https://issues.jboss.org/browse/JBEE-201?page=com.atlassian.jira.plugin.s... ] Jason Brock updated JBEE-201: ----------------------------- Description: Test issue please ignore Security sensitive checkbox only. was:Test issue please ignore > Test Issue - please ignore > -------------------------- > > Key: JBEE-201 > URL: https://issues.jboss.org/browse/JBEE-201 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Reporter: Jason Brock > Assignee: Jason Brock > Priority: Major > > Test issue please ignore > Security sensitive checkbox only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019