June 2020 - jboss-jira - Jboss List Archives

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

by Alexandru Ciouca (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Alexandru Ciouca updated WFLY-13559: ------------------------------------ Affects Version/s: 20.0.0.Final 19.0.0.Final > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final > Reporter: Alexandru Ciouca > Priority: Major > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13234) WF17 vs. WF18: org.infinispan.hibernate-cache

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13234?page=com.atlassian.jira.plugi... ] Scott Marlow resolved WFLY-13234. --------------------------------- Resolution: Explained > WF17 vs. WF18: org.infinispan.hibernate-cache > --------------------------------------------- > > Key: WFLY-13234 > URL: https://issues.redhat.com/browse/WFLY-13234 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final > Reporter: Daniel Wehrle > Assignee: Scott Marlow > Priority: Major > > Hi. > Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from NON_XA to NONE (default) and what are the implications? Can this lead to performance problems? > WF17 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <transaction mode="NON_XA"/> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > WF18 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > Best regards, > Daniel -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13234) WF17 vs. WF18: org.infinispan.hibernate-cache

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13234?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13234: ------------------------------------- [~daniel.wehrle] the change was made for [WFLY-10638] {quote} Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from NON_XA to NONE (default) and what are the implications? {quote} The NON_XA was being ignored, except that a warning would be logged. So, there should be zero impact from this change. {quote} Can this lead to performance problems? {quote} There shouldn't be any, the Infinispan internal code was updated, to not need/support the NON_XA mode anymore. > WF17 vs. WF18: org.infinispan.hibernate-cache > --------------------------------------------- > > Key: WFLY-13234 > URL: https://issues.redhat.com/browse/WFLY-13234 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 18.0.1.Final > Reporter: Daniel Wehrle > Assignee: Scott Marlow > Priority: Major > > Hi. > Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from NON_XA to NONE (default) and what are the implications? Can this lead to performance problems? > WF17 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <transaction mode="NON_XA"/> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > WF18 > {code} > <cache-container name="hibernate" module="org.infinispan.hibernate-cache"> > <local-cache name="entity"> > <object-memory size="10000"/> > <expiration max-idle="100000"/> > </local-cache> > {code} > Best regards, > Daniel -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

by Alexandru Ciouca (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Alexandru Ciouca updated WFLY-13559: ------------------------------------ Attachment: test-endpoint-BEANS-XML.war test-endpoint-WORKING.war test-endpoint-CONTEXT.war > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Affects Versions: 19.1.0.Final > Reporter: Alexandru Ciouca > Priority: Major > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5423) Fix java 11 usage with kie-pmml-new

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5423?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5423. ------------------------------------ > Fix java 11 usage with kie-pmml-new > ----------------------------------- > > Key: DROOLS-5423 > URL: https://issues.redhat.com/browse/DROOLS-5423 > Project: Drools > Issue Type: Bug > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Critical > Labels: TrustyAI > > Kie-pmml-new is broken when running under Java 11. > This is due to the missing jaxb api/implementations. > Solution should be to add a java-11 profile inside kie-pmml-compiler-commons/pom.xml > > {code:java} > // <profiles> > <profile> > <id>java11-pmml</id> > <activation> > <jdk>[11,)</jdk> > </activation> > <properties> > <jaxb.api.version>2.3.2</jaxb.api.version> > </properties> > <dependencies> > <dependency> > <groupId>org.jboss.spec.javax.xml.bind</groupId> > <artifactId>jboss-jaxb-api_2.3_spec</artifactId> > </dependency> > <dependency> > <groupId>org.glassfish.jaxb</groupId> > <artifactId>jaxb-runtime</artifactId> > </dependency> > </dependencies> > </profile> > </profiles> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1997) Upgrade jboss-logmanager to 2.1.16.Final

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/ELY-1997?page=com.atlassian.jira.plugin.... ] Sonia Zaldana updated ELY-1997: ------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1413 > Upgrade jboss-logmanager to 2.1.16.Final > ---------------------------------------- > > Key: ELY-1997 > URL: https://issues.redhat.com/browse/ELY-1997 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Build > Reporter: Farah Juma > Assignee: Sonia Zaldana > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1997) Upgrade jboss-logmanager to 2.1.16.Final

by Farah Juma (Jira)

Farah Juma created ELY-1997: ------------------------------- Summary: Upgrade jboss-logmanager to 2.1.16.Final Key: ELY-1997 URL: https://issues.redhat.com/browse/ELY-1997 Project: WildFly Elytron Issue Type: Component Upgrade Components: Build Reporter: Farah Juma Assignee: Sonia Zaldana -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5317) Scenario Simulation shows misleading data type if DMN applies a constraint

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5317?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5317: ------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 19-21 (from May 4)) > Scenario Simulation shows misleading data type if DMN applies a constraint > -------------------------------------------------------------------------- > > Key: DROOLS-5317 > URL: https://issues.redhat.com/browse/DROOLS-5317 > Project: Drools > Issue Type: Bug > Affects Versions: 7.37.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4582) Cell selection doesn't span the entire cell if you Insert RightMost Column

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4582?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4582: ------------------------------- Fix Version/s: 7.40.0.Final > Cell selection doesn't span the entire cell if you Insert RightMost Column > -------------------------------------------------------------------------- > > Key: DROOLS-4582 > URL: https://issues.redhat.com/browse/DROOLS-4582 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: CustomerFocus, drools-tools > Fix For: 7.40.0.Final > > Attachments: image-2019-10-01-10-50-42-411.png, span.webm > > > !image-2019-10-01-10-50-42-411.png|thumbnail! > Selection doesn't span entirely if you bind new column -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1164) Use catalog source for maistra and kiali

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1164?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1164. ---------------------------------- Resolution: Done [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/install-service...] job now allows to specify: * kiali-manifests: private catalog source for pre-release testing maintained by kiali qe. This is using quay.io/maistra/kiali-olm-cs:TAG catalog image. * servicemesh-manifests: private catalog source for pre-release testing maintained by maistra qe. This is using quay.io/maistra/servicemesh-olm-cs:TAG catalog image > Use catalog source for maistra and kiali > ---------------------------------------- > > Key: SWSQE-1164 > URL: https://issues.redhat.com/browse/SWSQE-1164 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to use Catalog source instead of Operator source in OCP 4.6 > [https://docs.openshift.com/container-platform/4.4/release_notes/ocp-4-4-r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 June 2020