February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10806) Add mixed domain tests for EAP 7.2.0

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-10806?page=com.atlassian.jira.plugin... ] Kabir Khan reassigned WFLY-10806: --------------------------------- Assignee: Kabir Khan > Add mixed domain tests for EAP 7.2.0 > ------------------------------------ > > Key: WFLY-10806 > URL: https://issues.jboss.org/browse/WFLY-10806 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Martin Simka > Assignee: Kabir Khan > Priority: Blocker > Labels: blocker-WF15 > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3624) In a scenario it should be possible to create 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: --------------------------------- Attachment: screencast-08-02-19-5.webm > In a scenario it should be possible to create 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: Gabriele Cardosi > 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-11688) Update subsystem tests to use EAP 7.2.0 rather than WF14

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11688?page=com.atlassian.jira.plugin... ] Kabir Khan moved WFCORE-4320 to WFLY-11688: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-11688 (was: WFCORE-4320) Component/s: Management (was: Management) Fix Version/s: (was: 8.0.0.Beta5) > Update subsystem tests to use EAP 7.2.0 rather than WF14 > -------------------------------------------------------- > > Key: WFLY-11688 > URL: https://issues.jboss.org/browse/WFLY-11688 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Blocker > Labels: blocker-WF16 > > Once EAP 7.2.0 is out, remove ModelTestControllerVersion.EAP_7_2_0_TMP and add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

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

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3624: ------------------------------------- Summary: In a scenario it should be possible to create 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: Gabriele Cardosi 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] (WFCORE-4320) Update subsystem tests to use EAP 7.2.0 rather than WF14

by Kabir Khan (Jira)

Kabir Khan created WFCORE-4320: ---------------------------------- Summary: Update subsystem tests to use EAP 7.2.0 rather than WF14 Key: WFCORE-4320 URL: https://issues.jboss.org/browse/WFCORE-4320 Project: WildFly Core Issue Type: Task Components: Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.Beta5 Once EAP 7.2.0 is out, remove ModelTestControllerVersion.EAP_7_2_0_TMP and add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4089) Update subsystem and core-model tests to use EAP 7.2.0 rather than WF14

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFCORE-4089?page=com.atlassian.jira.plugi... ] Kabir Khan reassigned WFCORE-4089: ---------------------------------- Assignee: Kabir Khan (was: Jeff Mesnil) > Update subsystem and core-model tests to use EAP 7.2.0 rather than WF14 > ----------------------------------------------------------------------- > > Key: WFCORE-4089 > URL: https://issues.jboss.org/browse/WFCORE-4089 > Project: WildFly Core > Issue Type: Task > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Blocker > Labels: blocker-WF16 > Fix For: 8.0.0.Beta5 > > > Once EAP 7.2.0 is out, remove ModelTestControllerVersion.EAP_7_2_0_TMP and add EAP_7_2_0 proper, and go through and adjust all the tests using the tmp version. I think this is ok, as there are some more advances subsystem tests which specify additional maven artifacts. Those maven artifacts will need to be updated to use the proper EAP 7.2.0 artifacts once it is released, and having to do this replacement will serve as a reminder. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11408) Upgrade HAL to 3.1.2.Final

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11408?page=com.atlassian.jira.plugin... ] Harald Pehl commented on WFLY-11408: ------------------------------------ Bumping version to 3.1.2.Final. The payload is fixed now. All linked issues have TD and PC. > Upgrade HAL to 3.1.2.Final > -------------------------- > > Key: WFLY-11408 > URL: https://issues.jboss.org/browse/WFLY-11408 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 16.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11408) Upgrade HAL to 3.1.2.Final

by Harald Pehl (Jira)

[ https://issues.jboss.org/browse/WFLY-11408?page=com.atlassian.jira.plugin... ] Harald Pehl updated WFLY-11408: ------------------------------- Summary: Upgrade HAL to 3.1.2.Final (was: Upgrade HAL to 3.1.1.Final) > Upgrade HAL to 3.1.2.Final > -------------------------- > > Key: WFLY-11408 > URL: https://issues.jboss.org/browse/WFLY-11408 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 16.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3614?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3614: ---------------------------------------- We need to use a new {{SessionEditorPresenter}} for DMN that has a custom {{DefaultPaletteFactory}} that can handle the place maximise and minimise events. The factory is injected with {{DefaultPaletteWidget}} for which the {{BS3PaletteWidgetImpl}} implementation handles showing/hiding the palette. We'll need to only show/hide if the Editor is "in" _graph mode_. {{SessionEditorPresenter}} is injected into the {{DMNDiagramEditor}} (and a similar class for the "standalone" webapp). > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.jboss.org/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 14-25-52.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- 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 edited comment on WFLY-11535 at 2/8/19 8:09 AM: ------------------------------------------------------------ Have successfully recreated this issue, with Keycloak taken out of the equation. We are now using the Wildfly 14 official docker image. Attached is the latest standalone-ha file, the only change being a tweak to use JDBC_PING within JGroups as per our original config. It is the standalone file dated 8/Feb/2019. If the 4 instances are started in a staggered fashion then they correctly form one cluster of 4. If they are started simultaneously then they form 4 individual clusters. This was not an issue when we had Keycloak 4.5 running on Wildfly 13. Incidentally we noticed there was a modcluster definition in the Wildfly distribution standalone file, but not our original Keycloak standalone. We don't think it is necessary because we are using tcp rather than multicast. In any case we get the same outcome with and without modcluster present. was (Author: ianrodgers): Have successfully recreated this issue, with Keycloak taken out of the equation. We are now using the Wildfly 14 official docker image. Attached is the latest standalone-ha file, the only change being a tweak to use JDBC_PING within JGroups as per our original config. It is the standalone file If the 4 instances are started in a staggered fashion then they correctly form one cluster of 4. If they are started simultaneously then they form 4 individual clusters. This was not an issue when we had Keycloak 4.5 running on Wildfly 13. Incidentally we noticed there was a modcluster definition in the Wildfly distribution standalone file, but not our original Keycloak standalone. We don't think it is necessary because we are using tcp rather than multicast. In any case we get the same outcome with and without modcluster present. > 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: 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019