September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-172) not possible to change volume mount path in wildfly operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-172?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFWIP-172: ------------------------------ Labels: operator (was: ) > not possible to change volume mount path in wildfly operator > ------------------------------------------------------------ > > Key: WFWIP-172 > URL: https://issues.jboss.org/browse/WFWIP-172 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > WildFly Operator > It looks like (I'm not much familiar with go) that volume mount path is [hard coded|https://github.com/wildfly/wildfly-operator/blob/master/pkg/control...] and cannot be changed. > EAP will need {{/opt/eap/standalone/data}} > Also [documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...] says it is {{/opt/jboss/wildfly/standalone/data}} but that is different from code's {{/wildfly/standalone/data}}. > Upstream issue: https://github.com/wildfly/wildfly-operator/issues/55 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4553) It is not possible to build executable model kjar with 10K+ rules

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4553?page=com.atlassian.jira.plugi... ] Mario Fusco moved KOGITO-315 to DROOLS-4553: -------------------------------------------- Project: Drools (was: Kogito) Key: DROOLS-4553 (was: KOGITO-315) Docs QE Status: NEW QE Status: NEW > It is not possible to build executable model kjar with 10K+ rules > ----------------------------------------------------------------- > > Key: DROOLS-4553 > URL: https://issues.jboss.org/browse/DROOLS-4553 > Project: Drools > Issue Type: Enhancement > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > At the moment it is not possible to build executable model kjar with 10K+ rules. This is caused by the fact that the whole model is kept in memory and then flushed into .java file at the end of compilation process. Doing this in stages should fix the problem. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-198) EAP Operator long-term strategy

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-198?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFWIP-198: ------------------------------ Labels: operator (was: ) > EAP Operator long-term strategy > ------------------------------- > > Key: WFWIP-198 > URL: https://issues.jboss.org/browse/WFWIP-198 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Facts: > # Operator creates and manges internaly several kubernetes objects; StatefulSet, Pod, Service, Routes. By rough estimation these kubernetes objects expose approximately 50 options[2]. Operator now expose approximately 10 options [1]. > # EAP7-1192 is currently designed in way operator is integral part of solution. You can not turn off operator to EAP7-1192 properly work. > # User cant touch internal Kubernetes objects. Operator manages them and can overwrite changes anytime. > So given these facts question is what is long-term strategy with Operator? > # Operator will provide all options of internal objects. Everything I am able to configure directly with Kubernetes objects I will be able to configure with Operator > # Operator will expose just most useful options. If user wants to make something special he has to "turn off" operator and to be on his own. (Loosing transaction support provided by EAP7-1192) > # Operator will expose just most useful options. If user wants to make something special he can and Operator won't overwritten his changes. (I dont know if it is feasible?) > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#pods... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#stat... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#serv... > https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/#ingr... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4544) Add support to abs(duration) function

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4544?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-4544: -------------------------------------- Assignee: Edson Tirelli (was: Matteo Mortari) > Add support to abs(duration) function > ------------------------------------- > > Key: DROOLS-4544 > URL: https://issues.jboss.org/browse/DROOLS-4544 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Affects Versions: 7.27.0.Final > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Major > Fix For: 7.28.0.Final > > > Extend the abs() function to support evaluating the absolute of a duration value. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12579) Tweak basic integration tests for OCSP to be able to run them in product branches

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-12579?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-12579: -------------------------------- Description: The following tests assert values checking the WildFly home web page: CertificateRevocationListTestCase,OcspResponderDownTestCase,OcspTestCase The title of the console home web page in WildFly contains the string "Welcome to WildFly", however, the title is different in our product branches. The task here is to remove the "WildFly" name so we can run the tests without issues in WildFly as well as in our product branches. was: The following tests assert values checking the WildFly home web page. The title of the console home web page in WildFly contains the string "Welcome to WildFly", however, the title is different in our product branches. The task here is to remove the "WildFly" name so we can run the tests without issues in WildFly as well as in our product branches. > Tweak basic integration tests for OCSP to be able to run them in product branches > --------------------------------------------------------------------------------- > > Key: WFLY-12579 > URL: https://issues.jboss.org/browse/WFLY-12579 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 18.0.0.Beta1 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > The following tests assert values checking the WildFly home web page: CertificateRevocationListTestCase,OcspResponderDownTestCase,OcspTestCase > The title of the console home web page in WildFly contains the string "Welcome to WildFly", however, the title is different in our product branches. > The task here is to remove the "WildFly" name so we can run the tests without issues in WildFly as well as in our product branches. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12577) Upgrade WildFly Core to 10.0.0.Final

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12577?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-12577: ------------------------------- Summary: Upgrade WildFly Core to 10.0.0.Final (was: Upgrade WildFly Core to 19.0.0.Final) > Upgrade WildFly Core to 10.0.0.Final > ------------------------------------ > > Key: WFLY-12577 > URL: https://issues.jboss.org/browse/WFLY-12577 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12579) Tweak basic integration tests for OCSP to be able to run them in product branches

by Yeray Borges (Jira)

Yeray Borges created WFLY-12579: ----------------------------------- Summary: Tweak basic integration tests for OCSP to be able to run them in product branches Key: WFLY-12579 URL: https://issues.jboss.org/browse/WFLY-12579 Project: WildFly Issue Type: Task Components: Test Suite Affects Versions: 18.0.0.Beta1 Reporter: Yeray Borges Assignee: Yeray Borges The following tests assert values checking the WildFly home web page. The title of the console home web page in WildFly contains the string "Welcome to WildFly", however, the title is different in our product branches. The task here is to remove the "WildFly" name so we can run the tests without issues in WildFly as well as in our product branches. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4513) s2i build fails at KieServerContainerVerifier without appropriate logging when kmodule.xml schema validation fails

by Hiroko Miura (Jira)

[ https://issues.jboss.org/browse/DROOLS-4513?page=com.atlassian.jira.plugi... ] Hiroko Miura updated DROOLS-4513: --------------------------------- Summary: s2i build fails at KieServerContainerVerifier without appropriate logging when kmodule.xml schema validation fails (was: s2i build fails at KieServerContainerVerifier if multiple listeners are set ) > s2i build fails at KieServerContainerVerifier without appropriate logging when kmodule.xml schema validation fails > ------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4513 > URL: https://issues.jboss.org/browse/DROOLS-4513 > Project: Drools > Issue Type: Bug > Components: build, kie server > Affects Versions: 7.14.0.Final, 7.18.0.Final, 7.24.0.Final > Environment: OpenShift 3.11 with rhdm72-prod-immutable-kieserver.yaml/rhdm73-prod-immutable-kieserver.yaml > Reporter: Hiroko Miura > Assignee: Ant Stephenson > Priority: Major > Labels: support > Attachments: ruleTest.zip > > > If multiple ksession are defined in kmodule.xml and Event Lister is set more than one ksession, s2i build fails at KieServerContainerVerifier with the following error. > {noformat} > [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT > java.lang.RuntimeException: Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:65) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:53) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:40) > at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:119) > at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:101) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - com.redhat.gss:ruleTest:1.0.0-SNAPSHOT not verified. > ERROR Aborting due to error code 1 from kie server container verification > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2382) JGroups version 4.0.13.Final.jar is causing memory leaks

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2382?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2382: -------------------------------- Hi [~rashmia5] Yes, a call would be good. Please contact me separately: bban at redhat dot com > JGroups version 4.0.13.Final.jar is causing memory leaks > -------------------------------------------------------- > > Key: JGRP-2382 > URL: https://issues.jboss.org/browse/JGRP-2382 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.13 > Environment: AIX machine 7.1 with JDK 1.8 > Reporter: Rashmi Acharya > Assignee: Bela Ban > Priority: Major > Attachments: dumps_TEST_node1_20190918_after_3_hours.zip, dumps_TEST_node1_20190918_right_after_restart.zip, dumps_TEST_node2_20190918_after_3_hours.zip, dumps_TEST_node2_20190918_right_after_restart.zip > > > We are observing a constant memory growth and leak with JGroup version 4.0.13 .. > One of our customer is having two node cluster environment and in one node we are observing org.Group.Messages which contain org.groups.Header and org.groups.Stack.ipAddress objects.. these are not getting cleared from memory.. > We dont see any exception related to Jgroups from logs and but it is causing a gradual emory growth and OOM. > Here is the Jgroups cluster configuration we have: > dynamic.cluster.property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT2;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000" /> > <FD_ALL timeout="20000" interval="15000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48" /> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000"/> > <pbcast.GMS print_local_addr="true" join_timeout="15000" /> > </config> > ================================= > dynamic.cluster.distribution_property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_port="&MULTICAST_NODE_PORT1;" /> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > </config> > ================================ > dynamic.cluster.lock.protocolStack > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT3;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_ALL timeout="20000" interval="5000"/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3 /> <pbcast.STABLE desired_avg_gossip="20000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > <FRAG2 frag_size="8096"/> > <CENTRAL_LOCK2/> > </config> -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2383) Remove most attributes from sample configurations

by Bela Ban (Jira)

Bela Ban created JGRP-2383: ------------------------------ Summary: Remove most attributes from sample configurations Key: JGRP-2383 URL: https://issues.jboss.org/browse/JGRP-2383 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 The sample configs have many attributes, e.g. {code:xml} <pbcast.NAKACK2 xmit_interval="500" xmit_table_num_rows="100" xmit_table_msgs_per_row="2000" xmit_table_max_compaction_time="30000" use_mcast_xmit="true" discard_delivered_msgs="true" /> {code} This is bad: if default values are changed, people need to upgrade their configs (which they usually don't!). In the above example, the only attribute that's really useful is {{xmit_interval}}, the others can be removed. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 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 2019