September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5121) Unable to add a new server in a server-group of older EAP 7 host controller that is managed by a newer EAP 7 Domain Controller

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFCORE-5121?page=com.atlassian.jira.plug... ] Bartosz Spyrko-Smietanko moved JBEAP-20160 to WFCORE-5121: ---------------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5121 (was: JBEAP-20160) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Affects Version/s: (was: 7.3.1.GA) (was: 7.2.8.GA) > Unable to add a new server in a server-group of older EAP 7 host controller that is managed by a newer EAP 7 Domain Controller > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-5121 > URL: https://issues.redhat.com/browse/WFCORE-5121 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Bartosz Spyrko-Smietanko > Assignee: Bartosz Spyrko-Smietanko > Priority: Major > Labels: customer, support-case-open > > I followed EAP 7.2 documentation [1] and have successfully configured a JBoss EAP 7.2.8 Domain Controller to Administer a JBoss EAP 7.1.6 Host Controller. > I have followed all the steps listed in there and believe the configuration is OK. Both the master DC and host slave hosts started fine. > The remote slave host "SlaveEAP71" registered successfully into the EAP 7.2.8 DC > Cf.>>> > {code:java} > ... > [Host Controller] 20:34:54,387 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.2.8.GA (WildFly Core 6.0.27.Final-redhat-00001) (Host Controller) started in 6162ms - Started 81 of 83 services (23 services are lazy, passive or on-demand) > ... > [Host Controller] 20:35:12,457 INFO [org.jboss.as.domain.controller] (Host Controller Service Threads - 9) WFLYHC0019: Registered remote slave host "SlaveEAP71", JBoss JBoss EAP 7.1.6.GA (WildFly 3.0.21.Final-redhat-00001) > ... > {code} > > However, when trying to add a new server in a server-group with profile copied from the older EAP 7.1.6 host , I'm not able to have this working. The following error always comes up on CLI started on EAP 7.2.8 Domain Controller > {code:java} > [domain@10.44.130.73:9990 /] /host=SlaveEAP71/server-config=SlaveJvm-EAP71:add(group=ServerGroup-eap71) > { > "outcome" => "failed", > "result" => {}, > "failure-description" => {"host-failure-descriptions" => {"SlaveEAP71" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYDC0075: Cannot synchronize the model due to missing extensions: [org.wildfly.extension.microprofile.opentracing-smallrye, org.wildfly.extension.microprofile.config-smallrye, org.wildfly.extension.ee-security]."}}, > "rolled-back" => true > } > [domain@10.44.130.73:9990 /] > {code} > > This is a the server group defined in the Host master domain.xml : > {code:java} > <server-groups> > <server-group name="ServerGroup-eap71" profile="full-ha-eap71"> > <socket-binding-group ref="full-ha-eap71-sockets"/> > </server-group> > </server-groups> > {code} > > The profile="full-ha-eap71" is copied from the EAP 7.1.6 domain.xml and added into EAP 7.2.8 domain.xml, as well as the "full-ha-eap71-sockets" socket-binding-group. > > *NOTE: The same issue does also happen with EAP 7.3.1 running as master host DC and EAP 7.1.6 as host slave.* > > [1] [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

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

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13793: ------------------------------------------ This comes from the fact that any queue/topic created with the embedded broker will have this prefix thus we are trying to be in Artemis 1.x mode. Some magic is also occurring with Artemis client/ra code so changing this behavior might have some impact. This needs careful testing as we don't want to create refgressions > 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 > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Beta1 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13350) Add a Galleon layer for JSF

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13350?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13350: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13532 (was: https://github.com/wildfly/wildfly/pull/13352) > Add a Galleon layer for JSF > --------------------------- > > Key: WFLY-13350 > URL: https://issues.redhat.com/browse/WFLY-13350 > Project: WildFly > Issue Type: Feature Request > Components: Build System, JSF > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > > Create a Galleon layer to provision the JSF subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5630) DMN Survey validation rules for missing element references

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5630?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5630: ---------------------------------------- Following up on [DROOLS-5414] to check if validation rules for missing element references are really enacted, and check for DS if all element references are present in the model (or imported models) > DMN Survey validation rules for missing element references > ---------------------------------------------------------- > > Key: DROOLS-5630 > URL: https://issues.redhat.com/browse/DROOLS-5630 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > dmn-validation-rules-dmnelementref.drl -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5630) DMN Survey validation rules for missing element references

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5630: -------------------------------------- Summary: DMN Survey validation rules for missing element references Key: DROOLS-5630 URL: https://issues.redhat.com/browse/DROOLS-5630 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari dmn-validation-rules-dmnelementref.drl -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5629) Document unsupported features in mining model

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5629: ------------------------------------ Summary: Document unsupported features in mining model Key: DROOLS-5629 URL: https://issues.redhat.com/browse/DROOLS-5629 Project: Drools Issue Type: Sub-task Reporter: Jiri Petrlik Assignee: Gabriele Cardosi -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5627) Document unsupported features in tree model

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5627: ------------------------------------ Summary: Document unsupported features in tree model Key: DROOLS-5627 URL: https://issues.redhat.com/browse/DROOLS-5627 Project: Drools Issue Type: Sub-task Reporter: Jiri Petrlik Assignee: Gabriele Cardosi -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5628) Document unsupported features in scorecards model

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5628: ------------------------------------ Summary: Document unsupported features in scorecards model Key: DROOLS-5628 URL: https://issues.redhat.com/browse/DROOLS-5628 Project: Drools Issue Type: Sub-task Reporter: Jiri Petrlik Assignee: Gabriele Cardosi -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5626) Document unsupported features in regression model

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5626: ------------------------------------ Summary: Document unsupported features in regression model Key: DROOLS-5626 URL: https://issues.redhat.com/browse/DROOLS-5626 Project: Drools Issue Type: Sub-task Reporter: Jiri Petrlik Assignee: Gabriele Cardosi -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5625) Document unsupported features in new PMML implementation

by Jiri Petrlik (Jira)

Jiri Petrlik created DROOLS-5625: ------------------------------------ Summary: Document unsupported features in new PMML implementation Key: DROOLS-5625 URL: https://issues.redhat.com/browse/DROOLS-5625 Project: Drools Issue Type: Story Reporter: Jiri Petrlik Assignee: Gabriele Cardosi Document unsupported features in new PMML implementation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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