September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5109) Ensure the log manager configurator is attached to the root logger

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5109?page=com.atlassian.jira.plug... ] James Perkins commented on WFCORE-5109: --------------------------------------- I've made this a blocker as it does cause issues with the logging subsystem where the the logging configuration is overwritten when the logging subsystem is processed. This is an issue when something like a file handler is used and {{append}} is set to {{false}}. The file will be closed and re-opened resulting in missing log messages. > Ensure the log manager configurator is attached to the root logger > ------------------------------------------------------------------ > > Key: WFCORE-5109 > URL: https://issues.redhat.com/browse/WFCORE-5109 > Project: WildFly Core > Issue Type: Bug > Components: Bootable JAR, Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 13.0.0.Final > > > The entry point for the bootable JAR configures a custom log context. The logging subsystem looks on the root logger of that context to locate the {{Configurator}} which was used to configure the context. The configurator should be attached to the root logger so the subsystem locate it. Without this the context will be reconfigured resulting in possible truncation of log messages. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5109) Ensure the log manager configurator is attached to the root logger

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5109?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-5109: ---------------------------------- Fix Version/s: 13.0.0.Final > Ensure the log manager configurator is attached to the root logger > ------------------------------------------------------------------ > > Key: WFCORE-5109 > URL: https://issues.redhat.com/browse/WFCORE-5109 > Project: WildFly Core > Issue Type: Bug > Components: Bootable JAR, Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 13.0.0.Final > > > The entry point for the bootable JAR configures a custom log context. The logging subsystem looks on the root logger of that context to locate the {{Configurator}} which was used to configure the context. The configurator should be attached to the root logger so the subsystem locate it. Without this the context will be reconfigured resulting in possible truncation of log messages. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5109) Ensure the log manager configurator is attached to the root logger

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5109?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-5109: ---------------------------------- Priority: Blocker (was: Major) > Ensure the log manager configurator is attached to the root logger > ------------------------------------------------------------------ > > Key: WFCORE-5109 > URL: https://issues.redhat.com/browse/WFCORE-5109 > Project: WildFly Core > Issue Type: Bug > Components: Bootable JAR, Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > > The entry point for the bootable JAR configures a custom log context. The logging subsystem looks on the root logger of that context to locate the {{Configurator}} which was used to configure the context. The configurator should be attached to the root logger so the subsystem locate it. Without this the context will be reconfigured resulting in possible truncation of log messages. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13774) Difference in OpenTracing subsystem standard configuration leads to the tests failures

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13774?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet edited comment on WFLY-13774 at 9/2/20 1:04 PM: ------------------------------------------------------------------ Using env variables the testsuite passes: export JAEGER_SAMPLER_TYPE=const export JAEGER_SAMPLER_PARAM=1.0 This was done to be 'consistent' with previous configuration which was relying on environment variables to configure opentracing. was (Author: ehugonnet): Using env variables the testsuite passes: export JAEGER_SAMPLER_TYPE=const export JAEGER_SAMPLER_PARAM=1.0 This was done to be 'consisten' with previous configuration which was relying on environment variables to configure opentracing. > Difference in OpenTracing subsystem standard configuration leads to the tests failures > --------------------------------------------------------------------------------------- > > Key: WFLY-13774 > URL: https://issues.redhat.com/browse/WFLY-13774 > Project: WildFly > Issue Type: Bug > Components: Build System, MP OpenTracing > Reporter: Sultan Zhantemirov > Assignee: Emmanuel Hugonnet > Priority: Major > > Since OpenTracing has been introduced, `standalone.xml` had the following OT SmallRye subsystem configuration: > {noformat} > <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0" default-tracer="jaeger"> > <jaeger-tracer name="jaeger"> > <sampler-configuration sampler-type="const" sampler-param="1.0"/> > </jaeger-tracer> > </subsystem> > {noformat} > With WildFly 19 and later we also have `standalone-microprofile.xml` configuration file which is used by default in MicroProfile test suite [1]. It has the following configuration: > {noformat} > <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0"/> > {noformat} > As it is recommended in documentation [2] it's better to define missing Jaeger properties (_sampler type _and _sampler param_) in order to sample every request. Sampling every request is needed by MicroProfile test suite OpenTracing basic tests. > A question is: will `standalone-microprofile.xml` configuration file have the wider OT subsystem configuration? Or do the tests have to define additional attributes in subsystem by themselves? > Thank you. > [1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite#target-distri... > [2] - https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13774) Difference in OpenTracing subsystem standard configuration leads to the tests failures

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13774?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13774: ------------------------------------------ Using env variables the testsuite passes: export JAEGER_SAMPLER_TYPE=const export JAEGER_SAMPLER_PARAM=1.0 This was done to be 'consisten' with previous configuration which was relying on environment variables to configure opentracing. > Difference in OpenTracing subsystem standard configuration leads to the tests failures > --------------------------------------------------------------------------------------- > > Key: WFLY-13774 > URL: https://issues.redhat.com/browse/WFLY-13774 > Project: WildFly > Issue Type: Bug > Components: Build System, MP OpenTracing > Reporter: Sultan Zhantemirov > Assignee: Emmanuel Hugonnet > Priority: Major > > Since OpenTracing has been introduced, `standalone.xml` had the following OT SmallRye subsystem configuration: > {noformat} > <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0" default-tracer="jaeger"> > <jaeger-tracer name="jaeger"> > <sampler-configuration sampler-type="const" sampler-param="1.0"/> > </jaeger-tracer> > </subsystem> > {noformat} > With WildFly 19 and later we also have `standalone-microprofile.xml` configuration file which is used by default in MicroProfile test suite [1]. It has the following configuration: > {noformat} > <subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0"/> > {noformat} > As it is recommended in documentation [2] it's better to define missing Jaeger properties (_sampler type _and _sampler param_) in order to sample every request. Sampling every request is needed by MicroProfile test suite OpenTracing basic tests. > A question is: will `standalone-microprofile.xml` configuration file have the wider OT subsystem configuration? Or do the tests have to define additional attributes in subsystem by themselves? > Thank you. > [1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite#target-distri... > [2] - https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5080) KeyStoresTestCase fails on IBM Java 8

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFCORE-5080?page=com.atlassian.jira.plug... ] Sonia Zaldana updated WFCORE-5080: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4314 > KeyStoresTestCase fails on IBM Java 8 > ------------------------------------- > > Key: WFCORE-5080 > URL: https://issues.redhat.com/browse/WFCORE-5080 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 13.0.0.Beta3 > Reporter: Ricardo Martin Camarero > Assignee: Sonia Zaldana > Priority: Major > > Same issue than WFCORE-5004 but in test case KeyStoresTestCase (inside elytron folder too). It's the same problem with the certificate comparison if using the EMAILADDRESS field. Previously it was hidden by the mock-server issue (WFCORE-5023). > [~szaldana] I'm assigning it to you, it's just repeating what you did for the previous JIRA but for the new class. If you don't have time or prefer that I do the JIRA just assign it back to me. Thanks a lot! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4708) Create an HACEP example with update kjar at runtime

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4708?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4708. --------------------------------- Resolution: Out of Date > Create an HACEP example with update kjar at runtime > --------------------------------------------------- > > Key: DROOLS-4708 > URL: https://issues.redhat.com/browse/DROOLS-4708 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4519) drools-android example not working

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4519?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4519. --------------------------------- Resolution: Out of Date We are no longer supporting android integration. > drools-android example not working > ---------------------------------- > > Key: DROOLS-4519 > URL: https://issues.redhat.com/browse/DROOLS-4519 > Project: Drools > Issue Type: Bug > Components: integration > Affects Versions: 7.26.0.Final > Reporter: Kamal Kumar > Assignee: Mario Fusco > Priority: Major > Labels: Android > > Do you have a working example of drools running on android? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5513) Issue while installing drools engine on wildfly

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5513?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5513. --------------------------------- Resolution: Incomplete Description Please clarify what you're attempting to do possibly also providing a reproducer. > Issue while installing drools engine on wildfly > ----------------------------------------------- > > Key: DROOLS-5513 > URL: https://issues.redhat.com/browse/DROOLS-5513 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.34.0.Final > Reporter: sumita sarkhel > Assignee: Mario Fusco > Priority: Critical > Labels: support > > Hi, > While calling buildAll() function, it throws the below error: > Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/interpolation/InterpolationException > at org.apache.maven.settings.building.DefaultSettingsBuilderFactory.newInstance(DefaultSettingsBuilderFactory.java:62) > at org.appformer.maven.integration.embedder.MavenSettings.initSettings(MavenSettings.java:91) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5578) Kie Server uses obselete/to be deleted Java APIs

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5578?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5578: -------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > Kie Server uses obselete/to be deleted Java APIs > ------------------------------------------------ > > Key: DROOLS-5578 > URL: https://issues.redhat.com/browse/DROOLS-5578 > Project: Drools > Issue Type: Component Upgrade > Components: kie server > Affects Versions: 7.38.0.Final, 7.39.0.Final, 7.40.0.Final, 7.41.0.Final > Reporter: Steve Davidson > Assignee: Mario Fusco > Priority: Minor > Labels: Kie-Server, kie, kie-server > > Kie Server is using several deprecated and soon to be restricted/deleted Java APIs. Much of this has been cleaned up over the last year or so, but there are still a few instances of old Java APIs in use. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020