February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13101) Tests for MicroProfile Health 2.2

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFLY-13101?page=com.atlassian.jira.plugi... ] Fabio Burzigotti commented on WFLY-13101: ----------------------------------------- This issue will be closed as necessary test coverage will be added to https://github.com/eclipse/microprofile-health/, see related issue [1] and discussion in [2] [1] https://github.com/eclipse/microprofile-health/issues/243 [2] https://github.com/wildfly/wildfly/pull/13004#issuecomment-587400544 > Tests for MicroProfile Health 2.2 > --------------------------------- > > Key: WFLY-13101 > URL: https://issues.redhat.com/browse/WFLY-13101 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 19.0.0.Beta2 > Reporter: Fabio Burzigotti > Assignee: Fabio Burzigotti > Priority: Major > Fix For: 19.0.0.Beta3 > > > Providing missing test coverage following the upgrade of MicroProfile Health to 2.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

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

by Andrew Marlow (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] Andrew Marlow commented on WFCORE-482: -------------------------------------- Thinking some more about wildfly using log4j2, and thinking about java logging in general, I am wondering if this enhancement request is really appropriate. If wildfly was changed then later on it might only need to be changed for log4j version 3, as and when that comes along. IMO it would be better for wildfly to use slf4j to wrap which logger is actually used. Given that wildfly is an application server, it is going to run code in a container where that code could use all sorts of other third party open source components. Those components could contain a mixture of logging approaches. So I think it is up to such components to use slf4j so that they can all play nicely together. If they did and wildfly still picked its own logger then that would be a shame. If on the other hand wildfly used slf4j then if any any contained component didn't that would be the fault of the contained component. Do people agree? If so then perhaps a new ticket should be raised for wildfly to use slf4j. Surely it is the best of both worlds, providing a way for it to still use log4j-v1 for those environments forced to use that logger, and to use log4j2 or logback or whatever, for everyone else. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13122) Include MicroProfile Fault Tolerance subsystem in the default server profiles

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13122: ------------------------------------- Summary: Include MicroProfile Fault Tolerance subsystem in the default server profiles Key: WFLY-13122 URL: https://issues.redhat.com/browse/WFLY-13122 Project: WildFly Issue Type: Bug Components: MP Fault Tolerance Affects Versions: 19.0.0.Beta2 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 19.0.0.Beta3, 20.0.0.Beta1 MP FT can be included in the default profiles. The subsystem is very lightweight, the subsystem carries no configuration and the module dependencies are not added to the deployments if the application is not using FT annotations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Keep file permissions when modifying an existing credential store

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/ELY-1890?page=com.atlassian.jira.plugin.... ] Ingo Weiss updated ELY-1890: ---------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1344, https://github.com/wildfly-security/wildfly-elytron/pull/1371 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1344) > Keep file permissions when modifying an existing credential store > ----------------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.redhat.com/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Bug > Components: Command-Line Tool > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-96) Update Travis to build using OpenJDK 8

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-96?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated ELYWEB-96: ----------------------------------- Summary: Update Travis to build using OpenJDK 8 (was: Update Travis to build using Java 11) > Update Travis to build using OpenJDK 8 > -------------------------------------- > > Key: ELYWEB-96 > URL: https://issues.redhat.com/browse/ELYWEB-96 > Project: Elytron Web > Issue Type: Task > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.6.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5073) menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18)

by xiaodong zhang (Jira)

[ https://issues.redhat.com/browse/DROOLS-5073?page=com.atlassian.jira.plug... ] xiaodong zhang commented on DROOLS-5073: ---------------------------------------- Thanks a lot for the quick response, Michael. That helps. Will check when 7.33 released. > menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18) > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5073 > URL: https://issues.redhat.com/browse/DROOLS-5073 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.19.0.Final > Reporter: xiaodong zhang > Assignee: Michael Anstis > Priority: Major > Fix For: 7.33.0.Final > > Attachments: maycolumns.dmn > > > Menu didn't pop up when right-click the cell in decition table if there are lot of columns (more then 18). > This happened on my macbook pro. If I use a External display. The things will be better but still hit the issue if the columns is more than 25。 > But this isn't happend on my new windows machine(i7 9th , GTX1660ti) > So I guess this a a performance issue, when shortage of the hardware resource， the UI will refreshed when right click the cell and caused the right-click menu gone. > Please help to check this . Thanks a lot ! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1935) Backport new MicroProfile JWT module

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1935?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1935: ---------------------------------- Summary: Backport new MicroProfile JWT module (was: Backport new MicroProifle JWT module) > Backport new MicroProfile JWT module > ------------------------------------ > > Key: ELY-1935 > URL: https://issues.redhat.com/browse/ELY-1935 > Project: WildFly Elytron > Issue Type: Bug > Components: MicroProfile > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.5.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-97) Release Elytron Web 1.6.1.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-97: -------------------------------------- Summary: Release Elytron Web 1.6.1.Final Key: ELYWEB-97 URL: https://issues.redhat.com/browse/ELYWEB-97 Project: Elytron Web Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.6.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5043) ConcurrentModificationException thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5043?page=com.atlassian.jira.plug... ] Luca Molteni commented on DROOLS-5043: -------------------------------------- Fixed here https://github.com/kiegroup/drools/commit/0e730cb98100cb0994c8bfb93ec7372... > ConcurrentModificationException thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5043 > URL: https://issues.redhat.com/browse/DROOLS-5043 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.33.0.Final > Reporter: Radovan Synek > Assignee: Luca Molteni > Priority: Critical > Attachments: stacktrace > > > CME is thrown from org.drools.modelcompiler.constraints.LambdaAccumulator.hashCode in OptaPlanner KIE Server extension tests. One of the failing tests is for example [1]. > The executable model is switched on because the test creates SolverFactory from KieContainer [2], that is already compiler via a kie-maven-plugin - see the corresponding testing KJAR [3]. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [3] https://github.com/kiegroup/droolsjbpm-integration/tree/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-96) Update Travis to build using Java 11

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-96: -------------------------------------- Summary: Update Travis to build using Java 11 Key: ELYWEB-96 URL: https://issues.redhat.com/browse/ELYWEB-96 Project: Elytron Web Issue Type: Task Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.6.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020