September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2500) Throttle "no route to" log messages

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2500?page=com.atlassian.jira.plugin... ] Bela Ban reassigned JGRP-2500: ------------------------------ Fix Version/s: 4.2.6 5.0.4 Assignee: Bela Ban > Throttle "no route to" log messages > ----------------------------------- > > Key: JGRP-2500 > URL: https://issues.redhat.com/browse/JGRP-2500 > Project: JGroups > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.6, 5.0.4 > > > When doing some put in a cache that has a backup site, if the backup site is not available, a lot of messages will be printed in logs. I think that we can count and print every 100 or 1000 > Current state: > {noformat} > [1;31m21:42:38,542 ERROR (jgroups-146,edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m > [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m > {noformat} > Desired state: dropping X messages > {noformat} > [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping X messages[m > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5433) DMN Strongly typed generate JSON Schema

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5433?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5433: ----------------------------------- Description: update: won't do. JSON Schema can be found as part of Swagger/Open API definition file (the endpoint payload in Swagger/openapi is a JSONSchema already) > DMN Strongly typed generate JSON Schema > --------------------------------------- > > Key: DROOLS-5433 > URL: https://issues.redhat.com/browse/DROOLS-5433 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > update: won't do. JSON Schema can be found as part of Swagger/Open API definition file (the endpoint payload in Swagger/openapi is a JSONSchema already) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5433) DMN Strongly typed generate JSON Schema

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5433?page=com.atlassian.jira.plug... ] Matteo Mortari resolved DROOLS-5433. ------------------------------------ Resolution: Won't Do > DMN Strongly typed generate JSON Schema > --------------------------------------- > > Key: DROOLS-5433 > URL: https://issues.redhat.com/browse/DROOLS-5433 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > update: won't do. JSON Schema can be found as part of Swagger/Open API definition file (the endpoint payload in Swagger/openapi is a JSONSchema already) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5605) [DMN Designer] Enabled elements in Read Only Mode

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5605?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-5605. ------------------------------- Resolution: Won't Fix > [DMN Designer] Enabled elements in Read Only Mode > ------------------------------------------------- > > Key: DROOLS-5605 > URL: https://issues.redhat.com/browse/DROOLS-5605 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.43.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Attachments: Screenshot from 2020-08-27 15-45-51.png, Screenshot from 2020-08-27 15-46-21.png > > > This issue is related to KOGITO-543. There are still two places to disable for Read Only mode. > h1. Navigate To Expression Editor > Currently an exception is thrown if user tries to open an expression editor for DMN node in read only mode. > !Screenshot from 2020-08-27 15-45-51.png|thumbnail! > h1. Import Data Object > There is button to generate DMN data type according to a java class. This button should be disabled in Read Only mode. > !Screenshot from 2020-08-27 15-46-21.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-344) Bootable JAR - SSL 8443 port doesn't work by default

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-344?page=com.atlassian.jira.plugin... ] Marek Kopecky reassigned WFWIP-344: ----------------------------------- Assignee: Jean Francois Denise (was: Kabir Khan) > Bootable JAR - SSL 8443 port doesn't work by default > ---------------------------------------------------- > > Key: WFWIP-344 > URL: https://issues.redhat.com/browse/WFWIP-344 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jean Francois Denise > Priority: Blocker > Attachments: ssl-war.war > > > RFE jira: EAP7-1385 > SSL 8443 port doesn't work by default on bootable jar > *Steps to reproduce:* > * start bootable jar (hollow jar) with jaxrs-server, microprofile-config, datasources, h2-default-datasource layers (you can check the same on WF) > * deploy deployment with this simple deployment ([^ssl-war.war]): > {code:java} > @Path("/ssl") > public class SslResource { > @Path("/hello") > @GET > public String hello() { > return "Hello World!"; > } > } > {code} > * Make HTTP call by this client (use [this client.truststore|https://github.com/resteasy/Resteasy/blob/3.12/testsuit...]): > {code:java} > truststore = KeyStore.getInstance("jks"); > try (InputStream in = new FileInputStream("/home/path/client.truststore")) { > truststore.load(in, "123456".toCharArray()); > } > resteasyClientBuilder = (ResteasyClientBuilder) ClientBuilder.newBuilder(); > resteasyClientBuilder.setIsTrustSelfSignedCertificates(false); > resteasyClientBuilder = resteasyClientBuilder.disableTrustManager(); > client = resteasyClientBuilder.trustStore(truststore).build(); > Response response = client.target("https://127.0.0.1:8443/ssl-war/ssl/hello").request().get(); > System.out.println("Response status: " + response.getStatus() + " (expected is 200)"); > if (response.getStatus() == 200) { > System.out.println("Output: " + response.readEntity(String.class)); > } > {code} > * See the results: > ** "Connection refused (Connection refused)" on bootable jar > ** 200 response code on WF > cc: [~fburzigo], [~yersan], [~asoldano], [~ron_sigal] -- 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 updated WFLY-13559: ------------------------------------ Component/s: MP OpenTracing > 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: Bartosz Baranowski > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-342) Bootable JAR - RESTEasy JAXB end-point return unexpected 400 response

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-342?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-342: -------------------------------------------- I can only reproduce with Bootable JAR, problem is unrelated to galleon. It is caused by some JBoss module magic done to set the proper JAXP factories at boot. I logged WFCORE-5110 > Bootable JAR - RESTEasy JAXB end-point return unexpected 400 response > --------------------------------------------------------------------- > > Key: WFWIP-342 > URL: https://issues.redhat.com/browse/WFWIP-342 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jean Francois Denise > Priority: Blocker > > RFE link: EAP7-1385 > RESTEasy JAXB end-point on bootable jar return unexpected 400 response with these security params: > {code:xml} > <context-param> > <param-name>resteasy.document.secure.processing.feature</param-name> > <param-value>true</param-value> > </context-param> > <context-param> > <param-name>resteasy.document.secure.disableDTDs</param-name> > <param-value>false</param-value> > </context-param> > <context-param> > <param-name>resteasy.document.expand.entity.references</param-name> > <param-value>false</param-value> > </context-param> > {code} > Used layers: > * jaxrs-server > * microprofile-config > Although this test is security related, AFAIK this is not related with legacy-security/elytron configuration, because related params are used in javax.xml.parsers.DocumentBuilderFactory directly from RESTEasy. Anyway let me know if I'm wrong. > Steps to reproduce: > # use installed WF version with reasonable layers, eg: WF_VERSION=21.0.0.Beta1-SNAPSHOT # > # git clone git@github.com:marekkopecky/Resteasy.git -b bootable-jar-3-12-secure-processing > # cd Resteasy > # mvn install -DskipTests -Dcheckstyle.skip=true > # cd testsuite > # mvn install:install-file -Dpackaging=pom -Dfile=pom.xml -DpomFile=pom.xml > # cd integration-tests > # mvn clean install -Dts.bootable -Ddefault=false -Ddisable.microprofile.tests -Dserver.version=${WF_VERSION} -Dserver.home=placeholder -Dcheckstyle.skip=true -Denforcer.skip -Dcheckstyle.skip=true -Dmaven.test.redirectTestOutputToFile=false > I can move these steps outside of TS, but I believe that TS doesn't affects this bootable jar behaviour, so it doesn't seem to be necessary. > I see just this unexpected&suspicious console output although I'm not sure whether it's related or not: > {noformat} > [org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 189; External DTD: Failed to read external DTD 'SecureProcessing_external.dtd', because 'file' access is not allowed due to restriction set by the accessExternalDTD property.] > {noformat} > cc: [~fburzigo], [~yersan], [~asoldano], [~ron_sigal] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5110) Bootable JAR doesn't setup the JAXP factories at boot

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-5110: -------------------------------------------- Summary: Bootable JAR doesn't setup the JAXP factories at boot Key: WFCORE-5110 URL: https://issues.redhat.com/browse/WFCORE-5110 Project: WildFly Core Issue Type: Bug Components: Bootable JAR Reporter: Jean Francois Denise Assignee: Jean Francois Denise We can observe invalid behavior such as WFWIP-342 -- 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 Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13559: ------------------------------------------ We are setting a second resteasy.providers context param instead of appending the filter to it so this might be the cause. > 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 > Assignee: Bartosz Baranowski > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5614) Executable model generates a non-compiling beta index when in an equal constraint the left type is not assignable from the right one

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5614: ----------------------------------- Summary: Executable model generates a non-compiling beta index when in an equal constraint the left type is not assignable from the right one Key: DROOLS-5614 URL: https://issues.redhat.com/browse/DROOLS-5614 Project: Drools Issue Type: Bug Components: executable model Reporter: Mario Fusco Assignee: Mario Fusco -- 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