September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13633) Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR

by Lin Gao (Jira)

[ https://issues.redhat.com/browse/WFLY-13633?page=com.atlassian.jira.plugi... ] Lin Gao updated WFLY-13633: --------------------------- Labels: downstream_dependency (was: ) > Undeployed CMR resource JNDI names are not deregisted as needing to be treated as CMR > ------------------------------------------------------------------------------------- > > Key: WFLY-13633 > URL: https://issues.redhat.com/browse/WFLY-13633 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > Labels: downstream_dependency > > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... does not remove the JNDI name from the list of names that Narayana will treat as CMR resources as it is removed from a copy of the map: https://github.com/jbosstm/narayana/blob/48818111d12d2e51b52082a00bcb6060... > This means that if Narayana encounters another resource at a later time with the same JNDI name it will consider it is a CMR resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5106) Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint.

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-5106?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-5106: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/4319) > Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint. > ------------------------------------------------------------------------------------------- > > Key: WFCORE-5106 > URL: https://issues.redhat.com/browse/WFCORE-5106 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint introduced by ELY-1211. > Add "encoding" attribute to "file-audit-log", "periodic-rotating-file-audit-log" and "size-rotating-file-audit-log" elements in Elytron subsystem to utilize the new feature introduced by ELY-1211. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5622) DMN small refactor to leverage BigDecimalMath in builtin functions

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5622: -------------------------------------- Summary: DMN small refactor to leverage BigDecimalMath in builtin functions Key: DROOLS-5622 URL: https://issues.redhat.com/browse/DROOLS-5622 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13559) Header response has changed and missing fields

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13559: ----------------------------------------- Thanks, [~alex.ciouca] for the report! > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final > Reporter: Alexandru Ciouca > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 21.0.0.Beta1 > > Attachments: standalone_18.0.0.final.xml, standalone_19.1.0.final.xml, test-endpoint-BEANS-XML.war, test-endpoint-CONTEXT.war, test-endpoint-WORKING.war > > > I have an application running in WildFly with some open endpoints to call and I tried an upgrade to WildFly 19.1.0.final from 18.0.0.final, but I noticed that something changed when calling the endpoints. In the Response Header I see that some of the fields are changed or are missing. Is this supposed to happen or do I need to add some extra configuration with WildFly 19? > Response WildFly 18.0.0.final: > {code} > HTTP/2 500 > cache-control: no-store, no-cache, must-revalidate > set-cookie: JSESSIONID=pLpPEvZZVekh0Bkqq06muz_cJ4_fmwxsqrt0HUdP.myservices-container-6f5b87f79d-ngzhf; path=/myservices > access-control-allow-headers: origin, content-type, accept, X-XSRF-TOKEN > content-type: application/json > content-length: 182 > link: <http://test.com/afs/rest>; rel="profile" > date: Thu, 04 Jun 2020 07:34:10 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=5ede0885e2c831c4946125e91d3facba; path=/; HttpOnly; Secure > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > Response WildFly 19.1.0.final: > {code} > HTTP/2 200 > set-cookie: JSESSIONID=9siDVU14OoFXojIIVxlMWbxNg1gcuSmLokwamY29.myservices-container-7c8dbf55f5-ctcks; path=/myservices > content-type: application/json > content-length: 182 > date: Thu, 04 Jun 2020 07:27:57 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=3edfc7a7549d107b41669532f6cb594a; path=/; HttpOnly; Secure > cache-control: private > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > As you can see the first thing that changed is the response code, even though the code is the same for both versions. The cache-control is also different and access-control-allow-headers and link fields are missing. > I am attaching also the standalone.xml for both versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13559) Header response has changed and missing fields

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13559: --------------------------------------- Fix Version/s: 21.0.0.Beta1 Assignee: Emmanuel Hugonnet (was: Bartosz Baranowski) Resolution: Done > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final > Reporter: Alexandru Ciouca > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 21.0.0.Beta1 > > Attachments: standalone_18.0.0.final.xml, standalone_19.1.0.final.xml, test-endpoint-BEANS-XML.war, test-endpoint-CONTEXT.war, test-endpoint-WORKING.war > > > I have an application running in WildFly with some open endpoints to call and I tried an upgrade to WildFly 19.1.0.final from 18.0.0.final, but I noticed that something changed when calling the endpoints. In the Response Header I see that some of the fields are changed or are missing. Is this supposed to happen or do I need to add some extra configuration with WildFly 19? > Response WildFly 18.0.0.final: > {code} > HTTP/2 500 > cache-control: no-store, no-cache, must-revalidate > set-cookie: JSESSIONID=pLpPEvZZVekh0Bkqq06muz_cJ4_fmwxsqrt0HUdP.myservices-container-6f5b87f79d-ngzhf; path=/myservices > access-control-allow-headers: origin, content-type, accept, X-XSRF-TOKEN > content-type: application/json > content-length: 182 > link: <http://test.com/afs/rest>; rel="profile" > date: Thu, 04 Jun 2020 07:34:10 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=5ede0885e2c831c4946125e91d3facba; path=/; HttpOnly; Secure > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > Response WildFly 19.1.0.final: > {code} > HTTP/2 200 > set-cookie: JSESSIONID=9siDVU14OoFXojIIVxlMWbxNg1gcuSmLokwamY29.myservices-container-7c8dbf55f5-ctcks; path=/myservices > content-type: application/json > content-length: 182 > date: Thu, 04 Jun 2020 07:27:57 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=3edfc7a7549d107b41669532f6cb594a; path=/; HttpOnly; Secure > cache-control: private > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > As you can see the first thing that changed is the response code, even though the code is the same for both versions. The cache-control is also different and access-control-allow-headers and link fields are missing. > I am attaching also the standalone.xml for both versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5106) Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint.

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-5106?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-5106: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4319 > Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint. > ------------------------------------------------------------------------------------------- > > Key: WFCORE-5106 > URL: https://issues.redhat.com/browse/WFCORE-5106 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > Add configuration option in Elytron subsystem to change file encoding in FileAuditEndpoint introduced by ELY-1211. > Add "encoding" attribute to "file-audit-log", "periodic-rotating-file-audit-log" and "size-rotating-file-audit-log" elements in Elytron subsystem to utilize the new feature introduced by ELY-1211. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13350) Add a Galleon layer for JSF

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13350?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13350: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13352 (was: https://github.com/wildfly/wildfly/pull/13330) > Add a Galleon layer for JSF > --------------------------- > > Key: WFLY-13350 > URL: https://issues.redhat.com/browse/WFLY-13350 > Project: WildFly > Issue Type: Feature Request > Components: Build System, JSF > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > > Create a Galleon layer to provision the JSF subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13826) EJB3SubsystemXMLPersister may omit the 'session-bean' wrapper element

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13826?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13826: ------------------------------------ Summary: EJB3SubsystemXMLPersister may omit the 'session-bean' wrapper element (was: EJB3SubsystemXMLPersister) > EJB3SubsystemXMLPersister may omit the 'session-bean' wrapper element > --------------------------------------------------------------------- > > Key: WFLY-13826 > URL: https://issues.redhat.com/browse/WFLY-13826 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 20.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > EJB3SubsystemXMLPersister checks the subsystem ModelNode for any of 3 child nodes and if present writes the start of a 'session-bean' element. Later it uses the same check and writes the closing tag. > But in between it check for other child nodes and does writing assuming the 'session-bean' element has been started. But it may not have been, which results in invalid xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13825) The 'microprofile.surefire' execution doesn't run microprofile tests at all due to wrong package name include

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13825?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13825: ----------------------------------------- Umm, that commit just moved an existing problem to a different spot :) https://github.com/wildfly/wildfly/commit/1226bd825d0271fa72e7280257c85dc... > The 'microprofile.surefire' execution doesn't run microprofile tests at all due to wrong package name include > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13825 > URL: https://issues.redhat.com/browse/WFLY-13825 > Project: WildFly > Issue Type: Bug > Affects Versions: 20.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 21.0.0.Beta1 > > > This is because the package name is actually "org/wildfly/test/integration/microprofile/**/*TestCase.java" and not "org/jboss/as/test/integration/microprofile/**/*TestCase.java". > Issue introduced in https://github.com/wildfly/wildfly/commit/1226bd825d0271fa72e7280257c85dc... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-331) Bootable JAR - module.path system property affects tests execution

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-331?page=com.atlassian.jira.plugin... ] Fabio Burzigotti commented on WFWIP-331: ---------------------------------------- Thanks [~jdenise] :) I'll do one last check on the EAP QE MicroProfile TS if you're okay with it. > Bootable JAR - module.path system property affects tests execution > ------------------------------------------------------------------- > > Key: WFWIP-331 > URL: https://issues.redhat.com/browse/WFWIP-331 > Project: WildFly WIP > Issue Type: Bug > Reporter: Fabio Burzigotti > Assignee: Jean Francois Denise > Priority: Major > > WIP commit [1] demonstrates failures affecting tests execution for the `intergation/microprofile-tck/metrics` module. > We're currently looking into those failures but we noticed that adding the `module.path` system property to the `surefire` plugin configuration would fix them [2]. > That property should not be taken into account by the bootable JAR Maven plugin ant the modules in that path should not belong to the bootable JAR as well. > [1] > https://github.com/fabiobrz/wildfly/commit/727d96332fcb6e7ae851e6be6b1858... > [2] > https://github.com/fabiobrz/wildfly/pull/14/files#diff-89c7e61b9f8f99978b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

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