May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-109) BBCode support for standalone version

by Ryszard Kozmik (JIRA)

BBCode support for standalone version ------------------------------------- Key: JBFORUMS-109 URL: http://jira.jboss.com/jira/browse/JBFORUMS-109 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.0.0 Alpha BBCode parser is now working only in portal environment. We need make it work as a standalone too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 week, 4 days

3
3
0 / 0

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3330: -------------------------------- Description: Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. Rationale: * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. was: Creating this jira to investigate if it would be possible to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. Rationale: * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. > DMN Properties panel - Style menu > --------------------------------- > > Key: DROOLS-3330 > URL: https://issues.jboss.org/browse/DROOLS-3330 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Optional > Labels: UX, UXTeam, drools-tools > Attachments: styles.png > > > Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. > Rationale: > * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. > * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. > * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

2 weeks

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 month, 2 weeks

2
3
0 / 0

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

2 months, 1 week

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)

2 months, 1 week

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

7 months, 1 week

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, 6 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, 6 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, 6 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, 6 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