June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5446) Guided rules (with DSL) fail to validate and compile

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5446?page=com.atlassian.jira.plug... ] Toni Rikkola moved JBPM-9190 to DROOLS-5446: -------------------------------------------- Project: Drools (was: jBPM) Key: DROOLS-5446 (was: JBPM-9190) Component/s: Guided Rule Editor (was: Workbench) Affects Version/s: 7.30.0.Final (was: 7.30.0.Final) > Guided rules (with DSL) fail to validate and compile > ---------------------------------------------------- > > Key: DROOLS-5446 > URL: https://issues.redhat.com/browse/DROOLS-5446 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.30.0.Final > Reporter: Jim West > Assignee: Toni Rikkola > Priority: Major > Labels: guided_rule_editor > Attachments: JBPM-9190.png, image-2020-06-16-09-53-53-312.png, image-2020-06-16-09-57-34-678.png, image-2020-06-16-09-58-21-349.png, image-2020-06-16-10-01-30-616.png, image-2020-06-16-10-08-22-707.png, my-building-project-kjar.zip, my-simple-model-1.0-SNAPSHOT.jar > > > A Business Central project with or without DSL definitions fails to compile when authoring a rule you choose *Use Domain Specific Language (DSL)* and tick on Show declared DSL sentences: > *!image-2020-06-16-10-08-22-707.png!* > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5446) Guided rules (with DSL) fail to validate and compile

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5446?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5446: --------------------------------- Labels: drools-tools guided_rule_editor (was: guided_rule_editor) > Guided rules (with DSL) fail to validate and compile > ---------------------------------------------------- > > Key: DROOLS-5446 > URL: https://issues.redhat.com/browse/DROOLS-5446 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.30.0.Final > Reporter: Jim West > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools, guided_rule_editor > Attachments: JBPM-9190.png, image-2020-06-16-09-53-53-312.png, image-2020-06-16-09-57-34-678.png, image-2020-06-16-09-58-21-349.png, image-2020-06-16-10-01-30-616.png, image-2020-06-16-10-08-22-707.png, my-building-project-kjar.zip, my-simple-model-1.0-SNAPSHOT.jar > > > A Business Central project with or without DSL definitions fails to compile when authoring a rule you choose *Use Domain Specific Language (DSL)* and tick on Show declared DSL sentences: > *!image-2020-06-16-10-08-22-707.png!* > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5445) DMN function adoc align sum([])

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5445?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5445: ----------------------------------- Description: align example as fully verifiable > DMN function adoc align sum([]) > ------------------------------- > > Key: DROOLS-5445 > URL: https://issues.redhat.com/browse/DROOLS-5445 > Project: Drools > Issue Type: Task > Components: dmn engine, docs > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > align example as fully verifiable -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5445) DMN function adoc align sum([])

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5445: -------------------------------------- Summary: DMN function adoc align sum([]) Key: DROOLS-5445 URL: https://issues.redhat.com/browse/DROOLS-5445 Project: Drools Issue Type: Task Components: dmn engine, docs Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5017) Upgrade jakarta.inject-api 1.0.1

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-5017: ----------------------------------- Summary: Upgrade jakarta.inject-api 1.0.1 Key: WFCORE-5017 URL: https://issues.redhat.com/browse/WFCORE-5017 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Reporter: Jeff Mesnil Tag: https://github.com/eclipse-ee4j/injection-api/releases/tag/1.0.1 Diff to previous integrated release: https://github.com/eclipse-ee4j/injection-api/compare/1.0...1.0.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1158) Mirror jaeger test environment images on disconnected environment

by Jeeva Kandasamy (Jira)

[ https://issues.redhat.com/browse/SWSQE-1158?page=com.atlassian.jira.plugi... ] Jeeva Kandasamy commented on SWSQE-1158: ---------------------------------------- [~kearls] Can you please add image details that needs to be mirrored to run E2E tests? Also we have to change the image path on the test. > Mirror jaeger test environment images on disconnected environment > ----------------------------------------------------------------- > > Key: SWSQE-1158 > URL: https://issues.redhat.com/browse/SWSQE-1158 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Priority: Major > > TODO: [~jkandasa] and [~kearls] will add the required image details here. > This ticket covers only the mirroring images. > Jaeger team has to modify test image url on there tests. example: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1967) Connection properties should be extracted automatically when creating a new Datasource

by Katarina Hermanova (Jira)

[ https://issues.redhat.com/browse/WFLY-1967?page=com.atlassian.jira.plugin... ] Katarina Hermanova reassigned WFLY-1967: ---------------------------------------- Assignee: Katarina Hermanova > Connection properties should be extracted automatically when creating a new Datasource > -------------------------------------------------------------------------------------- > > Key: WFLY-1967 > URL: https://issues.redhat.com/browse/WFLY-1967 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: Jay Wu > Assignee: Katarina Hermanova > Priority: Optional > Labels: JDBC, JDBC_connection, open_to_community > > When create a new Datasource, it needs to input the connection properties such as databaseName, serverName, user, password etc even also the datasouce class manually. > It should be enhanced for the ease for operation to extract the connection properties automatically when creating a new Datasource -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2

by Janardhan Naidu (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Janardhan Naidu commented on JGRP-2485: --------------------------------------- Hi [~belaban] Can you please provide some inputs on this. as we are unable to upgrade groups to 3.6.19 due as UDP is not working!. Thanks Janardhan > UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2 > -------------------------------------------------------------------- > > Key: JGRP-2485 > URL: https://issues.redhat.com/browse/JGRP-2485 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Reporter: Janardhan Naidu > Assignee: Bela Ban > Priority: Major > Attachments: noapp.log.D20200619.T053202_NODE1 > > > Hi Team, > > we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working. > after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP. > *Warnings:* > *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead* > [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField > *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored* > [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init > *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false* > > To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar: > and now our properties looks like: > *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2) > > > With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP. > Please help me in resolving the same > > Thank > Janardhan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13589) WildFly cannot connect to an infinispan-server cluster requiring authentication

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13589?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13589: ---------------------------------- Description: Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] See also: [https://infinispan.org/docs/dev/titles/server/server.html#security] was: Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] > WildFly cannot connect to an infinispan-server cluster requiring authentication > ------------------------------------------------------------------------------- > > Key: WFLY-13589 > URL: https://issues.redhat.com/browse/WFLY-13589 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > > Infinispan 11.0 requires authentication by default. Consequently, we need the ability to configure authentication for a remote-cache-container. > See: [https://infinispan.org/blog/2020/06/04/server-secure-by-default/] > See also: [https://infinispan.org/docs/dev/titles/server/server.html#security] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5015) Create 'core-specific' variants of Galleon feature groups and packages that are 'overridden' in full WildFly

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5015?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5015: ------------------------------------- Description: See [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html... background. For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP. Feature groups: domain-host-excludes domain-interfaces domain-profile host-master host-slave host standalone-profile Packages: bin.common bin.vaulttools docs.licenses.merge misc.common misc.domain misc.standalone was: See [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html... background. For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP. > Create 'core-specific' variants of Galleon feature groups and packages that are 'overridden' in full WildFly > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-5015 > URL: https://issues.redhat.com/browse/WFCORE-5015 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > See [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html... background. > For the wildfly-core galleon pack feature groups and packages that are 'overridden' in full WildFly, create a differently named variant in the galleon-common module that can be referenced in full WF. This eliminates the 'overriding/subclassing' and in a GAL-319 type future setup will allow the 'core' source item to be directly incorporated in the target FP in full without conflicting with an item with the same name in that target FP. > > Feature groups: > > domain-host-excludes > domain-interfaces > domain-profile > host-master > host-slave > host > standalone-profile > > Packages: > bin.common > bin.vaulttools > docs.licenses.merge > misc.common > misc.domain > misc.standalone > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 6 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 June 2020