February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4838) Upgrade slf4j-jboss-logmanager from 1.0.3.GA to 1.0.4.GA

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4838?page=com.atlassian.jira.plug... ] Bartosz Spyrko updated WFCORE-4838: ----------------------------------- Summary: Upgrade slf4j-jboss-logmanager from 1.0.3.GA to 1.0.4.GA (was: Upgrade slf4j-jboss-logmanager from 1.0.3.GA) > Upgrade slf4j-jboss-logmanager from 1.0.3.GA to 1.0.4.GA > -------------------------------------------------------- > > Key: WFCORE-4838 > URL: https://issues.redhat.com/browse/WFCORE-4838 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: Bartosz Spyrko > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4838) Upgrade slf4j-jboss-logmanager from 1.0.3.GA

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-4838?page=com.atlassian.jira.plug... ] Bartosz Spyrko moved JBEAP-18669 to WFCORE-4838: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4838 (was: JBEAP-18669) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Fix Version/s: (was: 7.3.1.GA) > Upgrade slf4j-jboss-logmanager from 1.0.3.GA > -------------------------------------------- > > Key: WFCORE-4838 > URL: https://issues.redhat.com/browse/WFCORE-4838 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Bartosz Spyrko > Assignee: Daniel Kreling > Priority: Major > Labels: downstream_dependency > > AMQ 7.4.0 upgraded to sfl4j-jboss-logmanager 1.0.4.GA.redhat-00001 > https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=907654 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5018) DMN internal refactor for itemDef isCollection/clone

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5018: -------------------------------------- Summary: DMN internal refactor for itemDef isCollection/clone Key: DROOLS-5018 URL: https://issues.redhat.com/browse/DROOLS-5018 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Avoid .setCollection() that means avoid clone() -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4024) Move keyboard shortcuts to menus in DMN.

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4024?page=com.atlassian.jira.plug... ] Elizabeth Clayton closed DROOLS-4024. ------------------------------------- Resolution: Done [~jomarko][~karreiro] Closing per your comments, addressed in https://github.com/kiegroup/kie-wb-common/pull/3125 > Move keyboard shortcuts to menus in DMN. > ---------------------------------------- > > Key: DROOLS-4024 > URL: https://issues.redhat.com/browse/DROOLS-4024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: currentMenu.png, insert+.png, kebab-shortcuts.png > > > As a business analyst practitioner, I would like to view the keyboard shortcuts in the context of the menu actions that they refer to. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13069) CoarseDatabasePersistenceWebFailoverTestCase fails intermittently

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFLY-13069?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFLY-13069: ----------------------------------- Assignee: (was: Brian Stansberry) > CoarseDatabasePersistenceWebFailoverTestCase fails intermittently > ----------------------------------------------------------------- > > Key: WFLY-13069 > URL: https://issues.redhat.com/browse/WFLY-13069 > Project: WildFly > Issue Type: Bug > Reporter: Yeray Borges > Priority: Major > > The following jobs kicked off by different PRs hit failures on CoarseDatabasePersistenceWebFailoverTestCase: > https://ci.wildfly.org/viewLog.html?buildId=185412&tab=buildResultsDiv&bu... > https://ci.wildfly.org/viewLog.html?buildId=185397&tab=buildResultsDiv&bu... > https://ci.wildfly.org/viewLog.html?buildId=184962&tab=buildResultsDiv&bu... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13069) CoarseDatabasePersistenceWebFailoverTestCase fails intermittently

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFLY-13069?page=com.atlassian.jira.plugi... ] Yeray Borges commented on WFLY-13069: ------------------------------------- Hello [~pferraro], do you think it could be still related to ISPN-10029? > CoarseDatabasePersistenceWebFailoverTestCase fails intermittently > ----------------------------------------------------------------- > > Key: WFLY-13069 > URL: https://issues.redhat.com/browse/WFLY-13069 > Project: WildFly > Issue Type: Bug > Reporter: Yeray Borges > Assignee: Brian Stansberry > Priority: Major > > The following jobs kicked off by different PRs hit failures on CoarseDatabasePersistenceWebFailoverTestCase: > https://ci.wildfly.org/viewLog.html?buildId=185412&tab=buildResultsDiv&bu... > https://ci.wildfly.org/viewLog.html?buildId=185397&tab=buildResultsDiv&bu... > https://ci.wildfly.org/viewLog.html?buildId=184962&tab=buildResultsDiv&bu... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13069) CoarseDatabasePersistenceWebFailoverTestCase fails intermittently

by Yeray Borges (Jira)

Yeray Borges created WFLY-13069: ----------------------------------- Summary: CoarseDatabasePersistenceWebFailoverTestCase fails intermittently Key: WFLY-13069 URL: https://issues.redhat.com/browse/WFLY-13069 Project: WildFly Issue Type: Bug Reporter: Yeray Borges Assignee: Brian Stansberry The following jobs kicked off by different PRs hit failures on CoarseDatabasePersistenceWebFailoverTestCase: https://ci.wildfly.org/viewLog.html?buildId=185412&tab=buildResultsDiv&bu... https://ci.wildfly.org/viewLog.html?buildId=185397&tab=buildResultsDiv&bu... https://ci.wildfly.org/viewLog.html?buildId=184962&tab=buildResultsDiv&bu... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2449) TCP/UDP: buffer size of 0 will not set buffer sizes

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2449?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2449. ---------------------------- Resolution: Done > TCP/UDP: buffer size of 0 will not set buffer sizes > --------------------------------------------------- > > Key: JGRP-2449 > URL: https://issues.redhat.com/browse/JGRP-2449 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0 > > > If we set (e.g.) {{mcast_recv_buf_size}} to {{0}}, then we won't set the buffer size, but will use whatever the OS default is. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4837) (7.3.z) [WFCORE-4596] Write lock is acquired reading patching resource using include-runtime

by Bartosz Spyrko (Jira)

Bartosz Spyrko created WFCORE-4837: -------------------------------------- Summary: (7.3.z) [WFCORE-4596] Write lock is acquired reading patching resource using include-runtime Key: WFCORE-4837 URL: https://issues.redhat.com/browse/WFCORE-4837 Project: WildFly Core Issue Type: Bug Components: Patching Reporter: Bartosz Spyrko Assignee: Yeray Borges Fix For: 11.0.0.Beta3 This is initially created as a bug but it needs first some investigation to discover if it is really necessary to acquire the write lock when the patching resource is read. If it is unnecessary, we should remove this need. The following operation is acquiring the write lock: {noformat} /host=slave/core-service=patching:read-resource(include-runtime=true) {noformat} It potentially will block if there is any other operation that has already acquired the lock. One consequence found due to this issue was HAL could block and hang if an HC is starting and the user clicks on 'Patching' menu entry. It was fixed in HAL, where an HC being restarted is no longer shown in the Patching menu. The main problem seems to be in PatchStreamResourceOperationStepHandler, which is the parent handler used for the handlers that manage patching operations. This parent handler is always acquiring the write lock. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4836) (7.3.z) Validate composite operation steps just before executing them

by Bartosz Spyrko (Jira)

Bartosz Spyrko created WFCORE-4836: -------------------------------------- Summary: (7.3.z) Validate composite operation steps just before executing them Key: WFCORE-4836 URL: https://issues.redhat.com/browse/WFCORE-4836 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Bartosz Spyrko Assignee: Yeray Borges Fix For: 9.0.0.Beta7, 9.0.0.Final Say we have a composite operation with 2 steps: 1) /extension=org.jboss.as.messaging:add 2) /subsystem=messaging:add This will fail: Failed to execute batch: JBAS014739: No handler for add at address [("subsystem" => "messaging")] This fails because at the time of validation the /subsystem=messaging:add is not valid. To illustrate, the execution order is Validate 1-2 1 2 A possible solution is to convert this to the following: V1 1 V2 (works now because 1 has registered the subsystem API) 2 I think that should work but it's a very complex area, particularly in a managed domain, so it's not at all certain this would prove feasible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 February 2020