October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2387) Message from a non-member causes FD_ALL to continually suspect it

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2387?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2387: --------------------------- Fix Version/s: 4.1.6 > Message from a non-member causes FD_ALL to continually suspect it > ----------------------------------------------------------------- > > Key: JGRP-2387 > URL: https://issues.jboss.org/browse/JGRP-2387 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.1 > Reporter: Dennis Reed > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.6 > > Attachments: Test.java > > > If a FD_SOCK control message from a non-member is seen by FD_SOCK, it will start continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a non-member triggers the issue. The issue is cleared on the next view change. > This does not cause any functional issues in the cluster, but can cause repeated WARN logs in some cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-223) disableHTTPRoute = true in runtime does not clean CR.status.hosts

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-223?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-223. ------------------------------ > disableHTTPRoute = true in runtime does not clean CR.status.hosts > ----------------------------------------------------------------- > > Key: WFWIP-223 > URL: https://issues.jboss.org/browse/WFWIP-223 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Reproducer: > # create CR > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: false > {code} > # Edit CR with disableHTTPRoute: true. I would expect Route object will be deleted. > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: true > {code} > # Route object eap-cd is not deleted but status.hosts is still filled > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > creationTimestamp: '2019-10-01T17:20:34Z' > generation: 2 > name: eap-cd > namespace: mchoma > resourceVersion: '629943' > selfLink: /apis/wildfly.org/v1alpha1/namespaces/mchoma/wildflyservers/eap-cd > uid: c7535f3f-e46f-11e9-b4ad-02e6008f3048 > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > disableHTTPRoute: false > env: [] > envFrom: [] > replicas: 1 > status: > hosts: > - >- > eap-cd-route-mchoma.apps.eap-qe-cluster105.eap-qe-cluster105.fw.rhcloud.com > pods: > - name: eap-cd-0 > podIP: 10.131.0.246 > state: ACTIVE > replicas: 1 > scalingdownPods: 0 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-961) Increase quota for security_group_rule in istio-dev PSI project

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-961?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-961. --------------------------------- Resolution: Done > Increase quota for security_group_rule in istio-dev PSI project > --------------------------------------------------------------- > > Key: SWSQE-961 > URL: https://issues.jboss.org/browse/SWSQE-961 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Default quota for security_group_rule is 400. One ocp 4.2 installation creates 50 rules. > We need to ask for higher quota -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4600) Embedded Camel endpoints don't work with executable model

by Tibor Zimanyi (Jira)

Tibor Zimanyi created DROOLS-4600: ------------------------------------- Summary: Embedded Camel endpoints don't work with executable model Key: DROOLS-4600 URL: https://issues.jboss.org/browse/DROOLS-4600 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.27.0.Final Reporter: Tibor Zimanyi Assignee: Luca Molteni When having and embedded Camel endpoint it DRL, it doesn't work with executable model. Reproducer can be found here [1]. For the test to reproduce the issue, it is needed to use executable model project in the buildAll() call here [2]. [1] https://github.com/kiegroup/droolsjbpm-integration/blob/5f95febee0c081310... [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-camel/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12593) Jakarta update to Quickstarts docs

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12593?page=com.atlassian.jira.plugin... ] Eduardo Martins closed WFLY-12593. ---------------------------------- Resolution: Duplicate Issue Dupe of WFLY-12594 > Jakarta update to Quickstarts docs > ---------------------------------- > > Key: WFLY-12593 > URL: https://issues.jboss.org/browse/WFLY-12593 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Any references to Java EE, in Quickstart docs, should be updated wrt Jakarta EE. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12630) Document usage of EJB and JMS Client BOM in Quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12630?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12630: ----------------------------------- Description: Similar to WFLY-12377, all Quickstarts should explain usage of the EJB Client and JMS Client BOMs, as the proper way to manage/use the dependencies in server, assuring compatibility with it. (was: All JAXWS Quickstarts should explain usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. Traditionally this kind of guidance is done along the reference to the BOM is pom.xml) > Document usage of EJB and JMS Client BOM in Quickstarts > ------------------------------------------------------- > > Key: WFLY-12630 > URL: https://issues.jboss.org/browse/WFLY-12630 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Similar to WFLY-12377, all Quickstarts should explain usage of the EJB Client and JMS Client BOMs, as the proper way to manage/use the dependencies in server, assuring compatibility with it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12630) Document usage of EJB and JMS Client BOM in Quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12630?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12630: ----------------------------------- Git Pull Request: (was: https://github.com/wildfly/quickstart/pull/363) > Document usage of EJB and JMS Client BOM in Quickstarts > ------------------------------------------------------- > > Key: WFLY-12630 > URL: https://issues.jboss.org/browse/WFLY-12630 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > All JAXWS Quickstarts should explain usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. Traditionally this kind of guidance is done along the reference to the BOM is pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12630) Document usage of EJB and JMS Client BOM in Quickstarts

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12630?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12630: ----------------------------------- Fix Version/s: (was: 18.0.0.Final) > Document usage of EJB and JMS Client BOM in Quickstarts > ------------------------------------------------------- > > Key: WFLY-12630 > URL: https://issues.jboss.org/browse/WFLY-12630 > Project: WildFly > Issue Type: Enhancement > Components: Quickstarts > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > All JAXWS Quickstarts should explain usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. Traditionally this kind of guidance is done along the reference to the BOM is pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12630) Document usage of EJB and JMS Client BOM in Quickstarts

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12630: -------------------------------------- Summary: Document usage of EJB and JMS Client BOM in Quickstarts Key: WFLY-12630 URL: https://issues.jboss.org/browse/WFLY-12630 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins Fix For: 18.0.0.Final All JAXWS Quickstarts should explain usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. Traditionally this kind of guidance is done along the reference to the BOM is pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4067) Add before/afterNodeEvaluated to enable monitoring of engine performance

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4067?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4067: -------------------------------- Sprint: 2019 Week 23-25, 2019 Week 41-43 (from Okt 7) (was: 2019 Week 23-25, 2019 Week 38-40 (from Sep 16)) > Add before/afterNodeEvaluated to enable monitoring of engine performance > ------------------------------------------------------------------------ > > Key: DROOLS-4067 > URL: https://issues.jboss.org/browse/DROOLS-4067 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019