February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3624) In a scenario it should be possible to create & edit only one item at a time in a collection

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3624?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3624: --------------------------------- Summary: In a scenario it should be possible to create & edit only one item at a time in a collection (was: In a scenario it should be possible to create only one item at a time in a collection) > In a scenario it should be possible to create & edit only one item at a time in a collection > -------------------------------------------------------------------------------------------- > > Key: DROOLS-3624 > URL: https://issues.jboss.org/browse/DROOLS-3624 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Anna Baker > Priority: Major > Labels: ScenarioSimulation > Attachments: screencast-08-02-19-5.webm > > > If you click multiple times on "Add item" button in the collection popup, it should open only one new item form -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously

by Ian Rodgers (Jira)

[ https://issues.jboss.org/browse/WFLY-11535?page=com.atlassian.jira.plugin... ] Ian Rodgers commented on WFLY-11535: ------------------------------------ For completeness have attached the Dockerfile and entrypoint scripts. > Cluster fails to merge if instances started simultaneously > ---------------------------------------------------------- > > Key: WFLY-11535 > URL: https://issues.jboss.org/browse/WFLY-11535 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Final > Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster > Reporter: Ian Rodgers > Assignee: Paul Ferraro > Priority: Major > Attachments: Dockerfile, docker-entrypoint.sh, entrypoint.sh, standalone-ha.xml, standalone-ha.xml > > > Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members). > We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join. > This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix. > On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously

by Ian Rodgers (Jira)

[ https://issues.jboss.org/browse/WFLY-11535?page=com.atlassian.jira.plugin... ] Ian Rodgers updated WFLY-11535: ------------------------------- Attachment: docker-entrypoint.sh Dockerfile entrypoint.sh > Cluster fails to merge if instances started simultaneously > ---------------------------------------------------------- > > Key: WFLY-11535 > URL: https://issues.jboss.org/browse/WFLY-11535 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.0.Final > Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster > Reporter: Ian Rodgers > Assignee: Paul Ferraro > Priority: Major > Attachments: Dockerfile, docker-entrypoint.sh, entrypoint.sh, standalone-ha.xml, standalone-ha.xml > > > Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members). > We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join. > This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix. > On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11570) Upgrade wildfly-transaction-client from 1.1.2.Final to 1.1.3.Final

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11570?page=com.atlassian.jira.plugin... ] Ondra Chaloupka reassigned WFLY-11570: -------------------------------------- Assignee: Ondra Chaloupka (was: David Lloyd) > Upgrade wildfly-transaction-client from 1.1.2.Final to 1.1.3.Final > ------------------------------------------------------------------ > > Key: WFLY-11570 > URL: https://issues.jboss.org/browse/WFLY-11570 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 15.0.1.Final > Reporter: Chao Wang > Assignee: Ondra Chaloupka > Priority: Major > > This is a placeholder as upstream dependency of 7.2.1 issue https://issues.jboss.org/browse/JBEAP-16091 > https://github.com/wildfly/wildfly-transaction-client/compare/1.1.2.Final... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11684) Upgrade WildFly Transaction Client to 1.1.3.Final

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11684?page=com.atlassian.jira.plugin... ] Ondra Chaloupka closed WFLY-11684. ---------------------------------- Resolution: Duplicate Issue Duplicit to WFLY-11570 > Upgrade WildFly Transaction Client to 1.1.3.Final > ------------------------------------------------- > > Key: WFLY-11684 > URL: https://issues.jboss.org/browse/WFLY-11684 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB, Transactions > Affects Versions: 15.0.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > > The WildFly Transaction client should be upgraded as it contains fixes for ejb transaction propagation of timeout handling. These fixes influences behaviour of the system. Those fixes are partly involved in the released EAP 7.2.0 and they are not in the WildFly upstream. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4322) Bump the kernel management API version to 10.0.0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4322?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4322: -------------------------------- Priority: Blocker (was: Major) > Bump the kernel management API version to 10.0.0 > ------------------------------------------------ > > Key: WFCORE-4322 > URL: https://issues.jboss.org/browse/WFCORE-4322 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 8.0.0.Beta1 > > > We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4322) Bump the kernel management API version to 10.0.0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4322?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4322: -------------------------------- Summary: Bump the kernel management API version to 10.0.0 (was: Bump the kernel management API version to 10.0.0 and the xsd to 10.0) > Bump the kernel management API version to 10.0.0 > ------------------------------------------------ > > Key: WFCORE-4322 > URL: https://issues.jboss.org/browse/WFCORE-4322 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > Fix For: 8.0.0.Beta1 > > > We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4322) Bump the kernel management API version to 10.0.0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4322?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4322: -------------------------------- Description: We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. When WFCORE-4247 was resolved, it only bumped the XML schema version to 10.0.0 but I forgot to bump the kernel management API version too. was:We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. > Bump the kernel management API version to 10.0.0 > ------------------------------------------------ > > Key: WFCORE-4322 > URL: https://issues.jboss.org/browse/WFCORE-4322 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 8.0.0.Beta1 > > > We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. > When WFCORE-4247 was resolved, it only bumped the XML schema version to 10.0.0 but I forgot to bump the kernel management API version too. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4322) Bump the kernel management API version to 10.0.0 and the xsd to 10.0

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4322: ----------------------------------- Summary: Bump the kernel management API version to 10.0.0 and the xsd to 10.0 Key: WFCORE-4322 URL: https://issues.jboss.org/browse/WFCORE-4322 Project: WildFly Core Issue Type: Task Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 8.0.0.Beta1 We know there are going to be API changes in WF Core 8, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-593) Upgrade rhel on all services hosts

by Filip Brychta (Jira)

Filip Brychta created SWSQE-593: ----------------------------------- Summary: Upgrade rhel on all services hosts Key: SWSQE-593 URL: https://issues.jboss.org/browse/SWSQE-593 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta We need to upgrade rhel on: * rhevm.jonqe.lab.eng.bos.redhat.com * foreman.jonqe.lab.eng.bos.redhat.com * jenkins2.bc.jonqe.lab.eng.bos.redhat.com * b01.jonqe.lab.eng.bos.redhat.com * netser.jonqe.lab.eng.bos.redhat.com * web.bc.jonqe.lab.eng.bos.redhat.com * backup.bc.jonqe.lab.eng.bos.redhat.com -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

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