September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13740) Upgrade Narayana to 5.10.6.Final

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13740?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka commented on WFLY-13740: ----------------------------------------- Release notes for Narayana 5.10.6.Final is available at: https://issues.redhat.com/secure/ReleaseNote.jspa?projectId=12310200&vers... > Upgrade Narayana to 5.10.6.Final > -------------------------------- > > Key: WFLY-13740 > URL: https://issues.redhat.com/browse/WFLY-13740 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Bartosz Spyrko-Smietanko > Assignee: Ondrej Chaloupka > Priority: Major > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Component upgrade of Narayana to version 5.10.6.Final. > This is to track fix for JBTM-3337 in Wildfly required by downstream -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13824) Use TimeUtil timeout adjustments in cases of timeout defined on JMS receive

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13824?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-13824: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13537 > Use TimeUtil timeout adjustments in cases of timeout defined on JMS receive > --------------------------------------------------------------------------- > > Key: WFLY-13824 > URL: https://issues.redhat.com/browse/WFLY-13824 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 20.0.1.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > There are several places in testsuite where is omitted usage of {{TimeoutUtil}} to allow adjustment of timeouts. When user defines the property {{-Dtimeout.factor}} when he runs the testsuite the waiting timeout for the JMS receival should be adjusted as well. > This issue comes from issues hit on Narayana CI. The machine is slow and running the WildFly testsuite with the Narayana SNAPSHOTs is unstable because of timeouts are not configurable at many places. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5092) Windows Service cannot be stopped when using custom JAVA_HOME path

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFCORE-5092?page=com.atlassian.jira.plug... ] Lukas Vydra commented on WFCORE-5092: ------------------------------------- Hi [~wraaflaub], I suppose that passing JAVA_HOME variable via /environment parameter is a supported solution. In the case of NO_PAUSE env variable, I don't think that calling jboss-cli.bat from service.bat with pausing makes any sense. So I have added NOPAUSE=Y to StopParams in PR. > Windows Service cannot be stopped when using custom JAVA_HOME path > ------------------------------------------------------------------ > > Key: WFCORE-5092 > URL: https://issues.redhat.com/browse/WFCORE-5092 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 11.0.0.Final > Reporter: Walter Raaflaub > Assignee: Lukas Vydra > Priority: Major > > I am running keycloak in a Wildfly container as a Windows service on Windows Server 2019. The service starts up and works correctly; but it hangs when I try to stop it. > There is no global JAVA_HOME environment variable defined on the server; I'm using a custom JAVA_HOME path that I have configured in standalone.conf.bat. > While stopping, the service issues the following warning in stdout.log: > {noformat} > JAVA_HOME is not set. Unexpected results may occur. > Set JAVA_HOME to the directory of your local JDK to avoid this message. > Drcken Sie eine beliebige Taste . . . > {noformat} > (Drücken Sie eine beliebige Taste . . . = German vor "Press any key ...") > It seems that when stopping the service, the JAVA_HOME setting is not correctly passed to the jboss-cli.bat script. The script seems to be waiting for user input, which is akward in a Windows service. That means that also the NOPAUSE setting is not passed correctly to the jboss-cli.bat script. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5111) Upgrade JBoss MSC from 1.4.11 to 1.4.12

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-5111?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-5111: ----------------------------------- Release Notes Text: https://github.com/jboss/xerces/compare/jboss-2.12.0.SP02...jboss-2.12.0.SP3 > Upgrade JBoss MSC from 1.4.11 to 1.4.12 > --------------------------------------- > > Key: WFCORE-5111 > URL: https://issues.redhat.com/browse/WFCORE-5111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 13.0.0.Beta6 > > > Brings in: > Fixes: > MSC-252 Removing double word of service in the thrown exception ServiceNotFoundException > Enhancements: > MSC-255 Deprecating StabilityMonitor & StabilityStatistics -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5111) Upgrade JBoss MSC from 1.4.11 to 1.4.12

by Richard Opalka (Jira)

[ https://issues.redhat.com/browse/WFCORE-5111?page=com.atlassian.jira.plug... ] Richard Opalka updated WFCORE-5111: ----------------------------------- Release Notes Text: (was: https://github.com/jboss/xerces/compare/jboss-2.12.0.SP02...jboss-2.12.0.SP3) > Upgrade JBoss MSC from 1.4.11 to 1.4.12 > --------------------------------------- > > Key: WFCORE-5111 > URL: https://issues.redhat.com/browse/WFCORE-5111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 13.0.0.Beta6 > > > Brings in: > Fixes: > MSC-252 Removing double word of service in the thrown exception ServiceNotFoundException > Enhancements: > MSC-255 Deprecating StabilityMonitor & StabilityStatistics -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[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)

4 years, 3 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)

4 years, 3 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)

4 years, 3 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)

4 years, 3 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)

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