August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-334) Bootable JAR - Cloud - Support for dns.DNS_PING

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-334: ------------------------------------------ Summary: Bootable JAR - Cloud - Support for dns.DNS_PING Key: WFWIP-334 URL: https://issues.redhat.com/browse/WFWIP-334 Project: WildFly WIP Issue Type: Feature Request Reporter: Jean Francois Denise Assignee: Jean Francois Denise Currently kubernetes.KUBE_PING is the protocol in use when cloud is enabled. KUBE_PING, although requiring an Openshift permission, is the simpler configuration wise (just need KUBERNETES namespace and your are done). DNS_PING doesn't require the extra permission but requires a new service (to expose the port 8888 in the pod) to be created. I propose that we keep KUBE_PING as the default protocol and extend the cloud element with a <ping-protocol>kubernetes.KUBE_PING|dns.DNS_PING</ping-protocol> element. The env variable used to set the service name is the same as EAP/XP S2I builder image: OPENSHIFT_DNS_PING_SERVICE_NAME web-clustering example will be evolved with a profile to support DNS_PING (and also to contain a yaml example file of the ping service). [~luck3y], [~mchoma], [~brian.stansberry] [~fburzigo] that is the proposal to also cover DNS_PING. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1204) UI Automations - Overview Enable Disable Auto Injection

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1204?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1204. ----------------------------------- Resolution: Done all PRs merged > UI Automations - Overview Enable Disable Auto Injection > ------------------------------------------------------- > > Key: SWSQE-1204 > URL: https://issues.redhat.com/browse/SWSQE-1204 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1875 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-333) Bootable JAR - Cloud - Remove https listener and self signed certificate

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-333: ------------------------------------------ Summary: Bootable JAR - Cloud - Remove https listener and self signed certificate Key: WFWIP-333 URL: https://issues.redhat.com/browse/WFWIP-333 Project: WildFly WIP Issue Type: Feature Request Reporter: Jean Francois Denise Assignee: Jean Francois Denise In a cloud context, having https listener and generation of self signed certificate is not recommended. When cloud is enabled, https listener and ssl identity will be removed. This does align with XP 1.0 S2i builder image configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-332) Bootable JAR - Cloud - Remove File handler from logging subsystem

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-332: ------------------------------------------ Summary: Bootable JAR - Cloud - Remove File handler from logging subsystem Key: WFWIP-332 URL: https://issues.redhat.com/browse/WFWIP-332 Project: WildFly WIP Issue Type: Feature Request Reporter: Jean Francois Denise Assignee: Jean Francois Denise For cloud, the logs are directed to the console not to a file, the subsystem must be updated to not configure a file handler. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5602) Review jbpm DMN examples version in codebase

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5602: -------------------------------------- Summary: Review jbpm DMN examples version in codebase Key: DROOLS-5602 URL: https://issues.redhat.com/browse/DROOLS-5602 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Fix For: 7.42.0.Final see Epic descr -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

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

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-13559: ----------------------------------------- Assignee: Bartosz Baranowski > 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)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5601) Review kogito-runtimes DMN examples version in codebase

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5601: -------------------------------------- Summary: Review kogito-runtimes DMN examples version in codebase Key: DROOLS-5601 URL: https://issues.redhat.com/browse/DROOLS-5601 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Fix For: 7.42.0.Final see Epic descr -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang edited comment on WFLY-13793 at 8/26/20 3:38 AM: ----------------------------------------------------------- setting an EnumValidator on attribute {{ENABLE_AMQ1_PREFIX}} of boolean type looks wrong at [https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/mai...] I have opened [https://github.com/wildfly/wildfly/pull/13505] to remove it. You can workaround the CLI command with : {code:xml} [standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name=enable-amq1-prefix, value=false) {code} was (Author: soul2zimate): setting an EnumValidator on attribute {{ENABLE_AMQ1_PREFIX}} of boolean type looks wrong at [https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/mai...] You can workaround the CLI command with : {code:xml} [standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name=enable-amq1-prefix, value=false) {code} > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Brian Stansberry > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5570) Share kie-dmn-versionconverter

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5570?page=com.atlassian.jira.plug... ] Matteo Mortari resolved DROOLS-5570. ------------------------------------ Resolution: Done done with https://github.com/kiegroup/kie-dmn-versionconverter > Share kie-dmn-versionconverter > ------------------------------ > > Key: DROOLS-5570 > URL: https://issues.redhat.com/browse/DROOLS-5570 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFLY-13793: ---------------------------------- setting an EnumValidator on attribute {{ENABLE_AMQ1_PREFIX}} of boolean type looks wrong at [https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/mai...] You can workaround the CLI command with : {code:xml} [standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name=enable-amq1-prefix, value=false) {code} > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Brian Stansberry > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020