August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- for the record, another build: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- again, 207 failed for messages on the output Queue on nodeD while the test is not looking for it in there: from print-data: queue id 116,count=1492 > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4059) Attribute 'always-send-client-cert' missing from ldapConnectionType in version 5, 6, 7, and 8 of the management schema

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4059?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4059: ---------------------------------- Fix Version/s: 6.0.0.CR4 (was: 6.0.0.CR3) > Attribute 'always-send-client-cert' missing from ldapConnectionType in version 5, 6, 7, and 8 of the management schema > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4059 > URL: https://issues.jboss.org/browse/WFCORE-4059 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.CR4 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4055) Activate jdk.unsupported module on modular JDK by default

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4055?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4055: ---------------------------------- Fix Version/s: 6.0.0.CR4 (was: 6.0.0.CR3) > Activate jdk.unsupported module on modular JDK by default > --------------------------------------------------------- > > Key: WFCORE-4055 > URL: https://issues.jboss.org/browse/WFCORE-4055 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security, Server, Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR4 > > > WildFlySecurityManager uses sun.misc.Unsafe. > Unsafe works only with jdk.unsupported module enabled. > jdk.unsupported is not resolved by default so we need to activate it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4049) Deactivate modular jdk properties we used in the past for workarounds.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4049?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4049: ---------------------------------- Fix Version/s: 6.0.0.CR4 (was: 6.0.0.CR3) > Deactivate modular jdk properties we used in the past for workarounds. > ---------------------------------------------------------------------- > > Key: WFCORE-4049 > URL: https://issues.jboss.org/browse/WFCORE-4049 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR4 > > > In the past we used the following properties: > -Dsun.util.logging.disableCallerCheck=true > -Djdk.attach.allowAttachSelf=true > to activate some workarounds on modular JDKs. > These workarounds are not needed anymore. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10908) Upgrade Hibernate Validator to 6.0.13.Final

by Guillaume Smet (JIRA)

Guillaume Smet created WFLY-10908: ------------------------------------- Summary: Upgrade Hibernate Validator to 6.0.13.Final Key: WFLY-10908 URL: https://issues.jboss.org/browse/WFLY-10908 Project: WildFly Issue Type: Component Upgrade Components: Bean Validation Reporter: Guillaume Smet Assignee: Guillaume Smet Fix For: 14.0.0.CR1 As discussed with Kabir, here is an update to HV fixing an encoding issue with the French translation and a few potential null pointer dereference bugs reported by Bharti. Changelog is here: https://hibernate.atlassian.net/browse/HV-1650?jql=project%20%3D%2010060%... . Commits: * https://github.com/hibernate/hibernate-validator/commit/d3858bc7c7c003d4b... * https://github.com/hibernate/hibernate-validator/commit/53fd14f7aa075dc06... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- Just to record another run: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- I started another build: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... But these tests keep failing for a test issue. [~eduda] Can you help me clearing this test up so I can eliminate that noise? Also: the test stopped the replica before live when I ran manually. Do you know in what circunstance that happens? I am playing with some possible options on clearing up tokens, but I need to understand this first. > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-119) [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-119?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFWIP-119: --------------------------------------- This last failure on 126 was the same thing... messages were on node4 and the count check did not work. > [Artemis 2.x upgrade] Lost message in replicated HA scenario with MDB > --------------------------------------------------------------------- > > Key: WFWIP-119 > URL: https://issues.jboss.org/browse/WFWIP-119 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Erich Duda > Assignee: Martyn Taylor > Priority: Blocker > > *Scenario* > * Start live/backup pair in replicated dedicated topology and start one more server which is in Artemis cluster with live. > * Send messages to queue InQueue. > * Start another server with MDB connected to cluster with live server which resend messages from InQueue to OutQueue. > * Stop backup server and then live server. > * Stop server which was in cluster with live server. > * Start live server and server in cluster. > * Start backup server. > The test fails because one message get lost. It wasn't sent to OutQueue. > Logs from failed test including traces you can find in \[1\]. > \[1\] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2874) Select a data type, inline, from DMN decision tables.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2874?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2874: ---------------------------------------- [~uxdlc] Yes, in the screenshot example "Decision-1" is the default (generated) name of the Decision node in the graph view; and yes it's expression is defined as a LiteralExpression; and yes it's Output data-type is "number". Finally, yes the drop-down for data-type supports "live search" (it uses the exact widget you linked). > Select a data type, inline, from DMN decision tables. > ----------------------------------------------------- > > Key: DROOLS-2874 > URL: https://issues.jboss.org/browse/DROOLS-2874 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type inline from a decision table. > * > Functional considerations/ pre conditions: > * Actions will be offered or spawned inline within the cells of decision tables. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018