December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFWIP-338) Bootable JAR - Cloud - Enable json logging

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFWIP-338?page=com.atlassian.jira.plugin... ] James Perkins commented on WFWIP-338: ------------------------------------- Sorry for the delay. I'd agree just a simple CLI example would be a good way to achieve this. The current logging example already does this, but just writes to a file instead. We could alter that to just write to the console instead of a file in that example. > Bootable JAR - Cloud - Enable json logging > ------------------------------------------ > > Key: WFWIP-338 > URL: https://issues.redhat.com/browse/WFWIP-338 > Project: WildFly WIP > Issue Type: Enhancement > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > In an openshift context it would be interesting to enable json logging. For Bootable JAR we would evolve the <cloud> element with <enable-json-logging>true|false</enable-json-logging>. > Logging subsystem and logging.properties would have to be updated during packaging. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4967) RequestController drops queued tasks randomly during server start.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4967?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned WFCORE-4967: ---------------------------------------- Assignee: P K (was: Jeff Mesnil) Resolution: Done > RequestController drops queued tasks randomly during server start. > ------------------------------------------------------------------ > > Key: WFCORE-4967 > URL: https://issues.redhat.com/browse/WFCORE-4967 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Final > Reporter: P K > Assignee: P K > Priority: Major > Fix For: 14.0.0.Beta4 > > > Our deployment is quite complex, EAR app containing several modules. > After move to different data-center some of EJB timers will not be triggered at all after server restart (randomly). > There was no change to wildfly server version and application itself. > Only hardware/network changed and issue started occurring. > Classified as : WEIRDO and some race conditions was assumed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5881) Persistable property not editable on data object

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5881?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-5881: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > Persistable property not editable on data object > ------------------------------------------------ > > Key: DROOLS-5881 > URL: https://issues.redhat.com/browse/DROOLS-5881 > Project: Drools > Issue Type: Enhancement > Reporter: Gabriele Cardosi > Assignee: Toni Rikkola > Priority: Minor > > "Persistable" property is available only during Data Object creation, but not on the Data Object editor. > There are other properties available on the right panel, but not this one; so if, by mistake, a user forgot to set that property on creation, (s)he have to recreate from beginning -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat 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 updated WFCORE-482: --------------------------------- Issue Type: Feature Request (was: Task) > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > Fix For: 14.0.0.Beta3 > > > 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)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5033) Move org.wildfly.security:wildfly-elytron-jacc into it's own module

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5033?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5033: -------------------------------- Fix Version/s: 14.0.0.Beta4 (was: 14.0.0.Beta3) > Move org.wildfly.security:wildfly-elytron-jacc into it's own module > ------------------------------------------------------------------- > > Key: WFCORE-5033 > URL: https://issues.redhat.com/browse/WFCORE-5033 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 14.0.0.Beta4 > > > Long term it will be desirable for JACC to be within it's own subsystem so it's inclusion can be controlled using layers, however there may be an intermediate step where we split JACC out from the Elytron project so will want to bring it in ideally in it's own module. > The classes within this module have never been public API so we are free to refactor as needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14131) Reactive Messaging Subsystem

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-14131?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFLY-14131: ------------------------------ Description: Currently this is to jot down what could be configured in a subsystem for the RM Kafka connector. * There are some classes set by properties. An example are the value (de)serializer classes. If someone wants to do custom ones, we also need the module name. * It looks like security is via SSL and certificates * There are a LOT of producer/consumer configuration properties. Since they seem stable (investigated [here|https://issues.redhat.com/browse/EAP7-1405?focusedCommentId=15515388...]), I'd rather not have to expose them via a subystem :) * We should also look at integration of the Kafka connector with MP Health was: Currently this is to jot down what could be configured in a subsystem for the RM Kafka connector. * There are some classes set by properties. An example are the value (de)serializer classes. If someone wants to do custom ones, we also need the module name. * It looks like security is via SSL and certificates * There are a LOT of producer/consumer configuration properties. Since they seem stable (investigated [here|https://issues.redhat.com/browse/EAP7-1405?focusedCommentId=15515388...]), I'd rather not have to expose them via a subystem :) > Reactive Messaging Subsystem > ---------------------------- > > Key: WFLY-14131 > URL: https://issues.redhat.com/browse/WFLY-14131 > Project: WildFly > Issue Type: Feature Request > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > > Currently this is to jot down what could be configured in a subsystem for the RM Kafka connector. > * There are some classes set by properties. An example are the value (de)serializer classes. If someone wants to do custom ones, we also need the module name. > * It looks like security is via SSL and certificates > * There are a LOT of producer/consumer configuration properties. Since they seem stable (investigated [here|https://issues.redhat.com/browse/EAP7-1405?focusedCommentId=15515388...]), I'd rather not have to expose them via a subystem :) > * We should also look at integration of the Kafka connector with MP Health -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5013) Remove the wildfly-openssl i386 and Solaris@x86_64 bindings

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5013?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5013: -------------------------------- Fix Version/s: 14.0.0.Beta4 (was: 14.0.0.Beta3) > Remove the wildfly-openssl i386 and Solaris@x86_64 bindings > ----------------------------------------------------------- > > Key: WFCORE-5013 > URL: https://issues.redhat.com/browse/WFCORE-5013 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Fix For: 14.0.0.Beta4 > > > We should remove the following bindings: > * wildfly-openssl-linux-i386 > * wildfly-openssl-windows-i386 > * wildfly-openssl-solaris-x86_64 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4967) RequestController drops queued tasks randomly during server start.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4967?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4967: ------------------------------------- Fix Version/s: 14.0.0.Beta4 > RequestController drops queued tasks randomly during server start. > ------------------------------------------------------------------ > > Key: WFCORE-4967 > URL: https://issues.redhat.com/browse/WFCORE-4967 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Final > Reporter: P K > Assignee: Jeff Mesnil > Priority: Major > Fix For: 14.0.0.Beta4 > > > Our deployment is quite complex, EAR app containing several modules. > After move to different data-center some of EJB timers will not be triggered at all after server restart (randomly). > There was no change to wildfly server version and application itself. > Only hardware/network changed and issue started occurring. > Classified as : WEIRDO and some race conditions was assumed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5185) Update ProviderDefinition to use optimised service loading API

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5185?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5185: -------------------------------- Fix Version/s: 14.0.0.Beta4 (was: 14.0.0.Beta3) > Update ProviderDefinition to use optimised service loading API > -------------------------------------------------------------- > > Key: WFCORE-5185 > URL: https://issues.redhat.com/browse/WFCORE-5185 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Priority: Major > Fix For: 14.0.0.Beta4 > > > A new API is being added to JBoss Modules to optimise how loaded services can be filtered, this will allow us to filter out the JDK provided security providers before they are instantiated. > Presently we can filter after instantiation which is wasted overhead during boot, including contributing the GC overhead. > Once this issue is available we can switch over: > https://issues.redhat.com/browse/MODULES-402 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5205) Use Module.findServices() to load Security Providers

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5205?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5205: -------------------------------- Fix Version/s: 14.0.0.Beta4 (was: 14.0.0.Beta3) > Use Module.findServices() to load Security Providers > ---------------------------------------------------- > > Key: WFCORE-5205 > URL: https://issues.redhat.com/browse/WFCORE-5205 > Project: WildFly Core > Issue Type: Enhancement > Components: Modules, Security > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 14.0.0.Beta4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020