August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13772) Upgrade Netty to 4.1.51.Final

by odidev PS (Jira)

[ https://issues.redhat.com/browse/WFLY-13772?page=com.atlassian.jira.plugi... ] odidev PS updated WFLY-13772: ----------------------------- Summary: Upgrade Netty to 4.1.51.Final (was: Upgrade Netty to 4.1.50.Final) > Upgrade Netty to 4.1.51.Final > ----------------------------- > > Key: WFLY-13772 > URL: https://issues.redhat.com/browse/WFLY-13772 > Project: WildFly > Issue Type: Component Upgrade > Reporter: odidev PS > Assignee: Brian Stansberry > Priority: Major > > Upgrade Netty to its latest version 4.1.50.Final which includes both security fixes and AArch64 performance improvements > Refer release notes for detail: [https://netty.io/news/2020/05/13/4-1-50-Final.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13772) Upgrade Netty to 4.1.50.Final

by odidev PS (Jira)

[ https://issues.redhat.com/browse/WFLY-13772?page=com.atlassian.jira.plugi... ] odidev PS commented on WFLY-13772: ---------------------------------- Upgrade to Netty 4.1.51.Final > Upgrade Netty to 4.1.50.Final > ----------------------------- > > Key: WFLY-13772 > URL: https://issues.redhat.com/browse/WFLY-13772 > Project: WildFly > Issue Type: Component Upgrade > Reporter: odidev PS > Assignee: Brian Stansberry > Priority: Major > > Upgrade Netty to its latest version 4.1.50.Final which includes both security fixes and AArch64 performance improvements > Refer release notes for detail: [https://netty.io/news/2020/05/13/4-1-50-Final.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

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

by Sultan Zhantemirov (Jira)

Sultan Zhantemirov created WFLY-13774: ----------------------------------------- Summary: 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 Reporter: Sultan Zhantemirov Assignee: Brian Stansberry 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)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5091) Upgrade WildFly Elytron 1.13.0.CR5

by Bartosz Spyrko-Smietanko (Jira)

Bartosz Spyrko-Smietanko created WFCORE-5091: ------------------------------------------------ Summary: Upgrade WildFly Elytron 1.13.0.CR5 Key: WFCORE-5091 URL: https://issues.redhat.com/browse/WFCORE-5091 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Bartosz Spyrko-Smietanko Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5091) Upgrade WildFly Elytron 1.13.0.CR5

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFCORE-5091?page=com.atlassian.jira.plug... ] Bartosz Spyrko-Smietanko updated WFCORE-5091: --------------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/4304) > Upgrade WildFly Elytron 1.13.0.CR5 > ---------------------------------- > > Key: WFCORE-5091 > URL: https://issues.redhat.com/browse/WFCORE-5091 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Bartosz Spyrko-Smietanko > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5091) Upgrade WildFly Elytron 1.13.0.CR5

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFCORE-5091?page=com.atlassian.jira.plug... ] Bartosz Spyrko-Smietanko updated WFCORE-5091: --------------------------------------------- Labels: downstream_dependency (was: ) > Upgrade WildFly Elytron 1.13.0.CR5 > ---------------------------------- > > Key: WFCORE-5091 > URL: https://issues.redhat.com/browse/WFCORE-5091 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Bartosz Spyrko-Smietanko > Assignee: Farah Juma > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-2016) Release WildFly Elytron 1.10.8.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-2016?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-2016. ----------------------------- Resolution: Done > Release WildFly Elytron 1.10.8.Final > ------------------------------------ > > Key: ELY-2016 > URL: https://issues.redhat.com/browse/ELY-2016 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.10.8.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13772) Upgrade Netty to 4.1.50.Final

by Frank Langelage (Jira)

[ https://issues.redhat.com/browse/WFLY-13772?page=com.atlassian.jira.plugi... ] Frank Langelage commented on WFLY-13772: ---------------------------------------- Version 4.1.51.Final is already available since a few weeks. [https://netty.io/news/2020/07/09/4-1-51-Final.html] > Upgrade Netty to 4.1.50.Final > ----------------------------- > > Key: WFLY-13772 > URL: https://issues.redhat.com/browse/WFLY-13772 > Project: WildFly > Issue Type: Component Upgrade > Reporter: odidev PS > Assignee: Brian Stansberry > Priority: Major > > Upgrade Netty to its latest version 4.1.50.Final which includes both security fixes and AArch64 performance improvements > Refer release notes for detail: [https://netty.io/news/2020/05/13/4-1-50-Final.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13770) Create jdbc job repository using deployment descriptors

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13770?page=com.atlassian.jira.plugi... ] Cheng Fang edited comment on WFLY-13770 at 8/17/20 4:09 PM: ------------------------------------------------------------ Looks like this doc section is out of date. It should use the latest schema namespace ({{urn:jboss:domain:batch-jberet:2.0}}), and use {{data-source}} attribute when defining a jdbc job repository: {code:xml} <jboss xmlns="urn:jboss:1.0"> <batch xmlns="urn:jboss:domain:batch-jberet:2.0"> <job-repository> <jdbc data-source="java:jboss/datasources/ExampleDS"/> </job-repository> </batch> </jboss> {code} Besides the doc, batch subsystem and tests also need to be updated to support this use case. was (Author: cfang): Looks like this doc section is out of date. It should use the latest schema namespace ({{urn:jboss:domain:batch-jberet:2.0}}), and use {{data-source}} attribute when defining a jdbc job repository: {code:xml} <jboss xmlns="urn:jboss:1.0"> <batch xmlns="urn:jboss:domain:batch-jberet:2.0"> <job-repository> <jdbc data-source="java:jboss/datasources/ExampleDS"/> </job-repository> </batch> </jboss> {code} > Create jdbc job repository using deployment descriptors > ------------------------------------------------------- > > Key: WFLY-13770 > URL: https://issues.redhat.com/browse/WFLY-13770 > Project: WildFly > Issue Type: Enhancement > Components: Batch > Affects Versions: 20.0.1.Final > Reporter: Jurij Bernhardt > Assignee: Cheng Fang > Priority: Major > > The Example for "new Job Repository" ([https://docs.wildfly.org/20/Admin_Guide.html#deployment-descriptors]) doesn't work properly. > {code:xml} > <jboss xmlns="urn:jboss:1.0"> > <batch xmlns="urn:jboss:batch-jberet:1.0"> > <job-repository> > <jdbc jndi-name="java:jboss/datasources/ExampleDS"/> > </job-repository> > </batch> > </jboss> > {code} > Schema batch-jberet_1_0.xsd alllows only in-memory or named job-repositoryType. > You get the validation exception by using the jdbc example. > It would be useful to improve the batch-jberet integration so that the example given above would work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13773) SFSB expiration does not trigger activation listener prior to removal

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13773: ----------------------------------- Summary: SFSB expiration does not trigger activation listener prior to removal Key: WFLY-13773 URL: https://issues.redhat.com/browse/WFLY-13773 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro As a side effect of this, the passivated count is never decremented in the expiration case, resulting in inaccurate statistics. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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