March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13285) Observability TCKs fail when -Dtestsuite.default.build.project.prefix=ee- is used

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13285: --------------------------------------- Summary: Observability TCKs fail when -Dtestsuite.default.build.project.prefix=ee- is used Key: WFLY-13285 URL: https://issues.redhat.com/browse/WFLY-13285 Project: WildFly Issue Type: Bug Components: MP Config, MP Health, MP Metrics, MP OpenTracing, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 20.0.0.Beta1 Switching to using standalone-microprofile.xml as the default config file used by test servers when the MP TCKs run broke the -Dtestsuite.default.build.project.prefix=ee- test setup that was part of WFLY-12985. (See recent https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 results.). This is because the config/health/metrics/opentracing tcks will run against a server based on the ee-build output if that property is set, and those server's don't provide standalone-microprofile.xml. Fix is to configure surefire/arquillian to use standalone.xml if that property is set. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13284) Fix incorrect method call in EJB3IIOPResource write-attribute handler

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13284?page=com.atlassian.jira.plugi... ] Richard Achmatowicz updated WFLY-13284: --------------------------------------- Summary: Fix incorrect method call in EJB3IIOPResource write-attribute handler (was: Fix incorrect method call in EJB3IIOP write-attribute handler) > Fix incorrect method call in EJB3IIOPResource write-attribute handler > --------------------------------------------------------------------- > > Key: WFLY-13284 > URL: https://issues.redhat.com/browse/WFLY-13284 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 19.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 19.0.1.Final > > > In the write-attribute handler for the ENABLE_BY_DEFAULT attribute, the wrong method is being called when adjusting the Runtime service to reflect the change to the attribute value. This was due to an inadvertent error when setting up write handlers for two attributes. In short, in the write handler for ENABLE_BY_DEFAULT: > {noformat} > service.setUseQualifiedName(value); > {noformat} > should be > {noformat} > service.setEnableByDefault(value); > {noformat} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13284) Fix incorrect method call in EJB3IIOP write-attribute handler

by Richard Achmatowicz (Jira)

Richard Achmatowicz created WFLY-13284: ------------------------------------------ Summary: Fix incorrect method call in EJB3IIOP write-attribute handler Key: WFLY-13284 URL: https://issues.redhat.com/browse/WFLY-13284 Project: WildFly Issue Type: Bug Components: IIOP Affects Versions: 19.0.0.Final Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Fix For: 19.0.1.Final In the write-attribute handler for the ENABLE_BY_DEFAULT attribute, the wrong method is being called when adjusting the Runtime service to reflect the change to the attribute value. This was due to an inadvertent error when setting up write handlers for two attributes. In short, in the write handler for ENABLE_BY_DEFAULT: {noformat} service.setUseQualifiedName(value); {noformat} should be {noformat} service.setEnableByDefault(value); {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5194) [DMN Designer] List: Remove header

by Michael Anstis (Jira)

Michael Anstis created DROOLS-5194: -------------------------------------- Summary: [DMN Designer] List: Remove header Key: DROOLS-5194 URL: https://issues.redhat.com/browse/DROOLS-5194 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.34.0.Final Reporter: Michael Anstis Assignee: Michael Anstis Fix For: 7.36.0.Final Errors when importing DMN model including the Boxed List semantic {{PreviewDiagramScreenActivity failed in OPEN: java.lang.RuntimeException: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent@cc23, FromClient=1 sent to [unavailable]}} We are lacking the support for "Boxed List" semantic, as described page 107 here : https://www.omg.org/spec/DMN/1.2/PDF See page 149, "10.5.4 List metamodel" The boxed list are represented by separate grid, similar to the Relation grid, however there is single column and no header cell. Other cells can be literal expressions or contexts. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5194) [DMN Designer] List: Remove header

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5194?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5194: ----------------------------------- Description: Further to DROOLS-5131 it is incorrect for the {{List}} to have any header. (was: Errors when importing DMN model including the Boxed List semantic {{PreviewDiagramScreenActivity failed in OPEN: java.lang.RuntimeException: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent@cc23, FromClient=1 sent to [unavailable]}} We are lacking the support for "Boxed List" semantic, as described page 107 here : https://www.omg.org/spec/DMN/1.2/PDF See page 149, "10.5.4 List metamodel" The boxed list are represented by separate grid, similar to the Relation grid, however there is single column and no header cell. Other cells can be literal expressions or contexts. ) > [DMN Designer] List: Remove header > ---------------------------------- > > Key: DROOLS-5194 > URL: https://issues.redhat.com/browse/DROOLS-5194 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.36.0.Final > > > Further to DROOLS-5131 it is incorrect for the {{List}} to have any header. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-263) Logger Lookup is much slower as with JDK 8

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-263?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-263: --------------------------------- Priority: Critical (was: Major) > Logger Lookup is much slower as with JDK 8 > ------------------------------------------ > > Key: LOGMGR-263 > URL: https://issues.redhat.com/browse/LOGMGR-263 > Project: JBoss Log Manager > Issue Type: Bug > Environment: WildFly 17, OpenJDK 11 > Reporter: Andreas Liebscher > Priority: Critical > Attachments: ClassInEar.java, LogContextCacher.java, getlogger-stack.txt, grafik1570016303722 (1).png, grafik1570016303722.png, grafik1570016791285.png, logger-demo.war, responsetimes.png > > > During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK 11 we had a serious performance issue. We identified the usage of the logging framework SLF4J with the pattern `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a performance improvement with the added `static` keyword. > Please check the VisualVM output as prove of JDKSpecific got slower: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-263) Logger Lookup is much slower as with JDK 8

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-263?page=com.atlassian.jira.plugi... ] James Perkins reassigned LOGMGR-263: ------------------------------------ Assignee: James Perkins > Logger Lookup is much slower as with JDK 8 > ------------------------------------------ > > Key: LOGMGR-263 > URL: https://issues.redhat.com/browse/LOGMGR-263 > Project: JBoss Log Manager > Issue Type: Bug > Environment: WildFly 17, OpenJDK 11 > Reporter: Andreas Liebscher > Assignee: James Perkins > Priority: Critical > Attachments: ClassInEar.java, LogContextCacher.java, getlogger-stack.txt, grafik1570016303722 (1).png, grafik1570016303722.png, grafik1570016791285.png, logger-demo.war, responsetimes.png > > > During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK 11 we had a serious performance issue. We identified the usage of the logging framework SLF4J with the pattern `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a performance improvement with the added `static` keyword. > Please check the VisualVM output as prove of JDKSpecific got slower: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4770) Design review/recommendations for Decision Table merged view

by Sarah Rambacher (Jira)

[ https://issues.redhat.com/browse/DROOLS-4770?page=com.atlassian.jira.plug... ] Sarah Rambacher commented on DROOLS-4770: ----------------------------------------- Here's a link to what [~jschuler-boss] did - you can use the grid icon in the header to merge cells. We didn't have a collapse as is shown in the video on DROOLS-3580 though. http://kogito.surge.sh/ [~manstis] [~uxdlc] > Design review/recommendations for Decision Table merged view > ------------------------------------------------------------ > > Key: DROOLS-4770 > URL: https://issues.redhat.com/browse/DROOLS-4770 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.17.0.Final > Reporter: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > > Review the visual presentation of the {{DecisionTableGrid}} in _merged_ mode, to access usability enhancements. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4892) Remove the ch.qos.cal10n module

by James Perkins (Jira)

James Perkins created WFCORE-4892: ------------------------------------- Summary: Remove the ch.qos.cal10n module Key: WFCORE-4892 URL: https://issues.redhat.com/browse/WFCORE-4892 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins The {{ch.qos.cal10n}} is private and no longer used. This was a requirement for the {{org.slf4j.ext}} module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-482: -------------------------------------- That is excellent feedback. Thanks [~xf01213]. > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/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: Major > > 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 (v7.13.8#713008)

6 years, 1 month

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 March 2020