September 2020 - jboss-jira - Jboss List Archives

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

by Richard Opalka (Jira)

Richard Opalka created WFCORE-5111: -------------------------------------- Summary: 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 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)

5 years, 8 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-344?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-344: ---------------------------------------- I would say the behaviour is the same across WildFly and bootable jar, the only difference is only a subset of layers is being provisioned here - the WildFly distribution on the other hand provisions a complete default. For this specific example if you add the "undertow-legacy-https" layer to the list you should have the legacy realm definition and the HTTPS listener although we need to move this general approach into a more sustainable practice. > 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)

5 years, 8 months

1
0
0 / 0

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

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-344?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-344: -------------------------------------------- [~mkopecky], I think the same occurs with WildFly using galleon to provision these layers. If you want https enabled, you can use the default config. To do so don't set any galleon layers, standalone-microprofile.xml will be used. In this config we include the undertow-legacy-https (that relies on security-realm and self signed certificate). > 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)

5 years, 8 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 commented on WFWIP-344: ------------------------------------- Do we want different behaviour in WF and bootable jar? > 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)

5 years, 8 months

1
0
0 / 0

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

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-344?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-344: ---------------------------------------- This sounds to be the expected behaviour, there is an example in the wildfly jar plugin project to active SSL so just sounds as though it is not activated. > 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)

5 years, 8 months

1
0
0 / 0

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

5 years, 8 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)

5 years, 8 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)

5 years, 8 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)

5 years, 8 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)

5 years, 8 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