April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4722) Refactor DOMUtil.createNodeAtPosition

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4722?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4722: ------------------------------- Priority: Optional (was: Major) > Refactor DOMUtil.createNodeAtPosition > ------------------------------------- > > Key: DROOLS-4722 > URL: https://issues.redhat.com/browse/DROOLS-4722 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Optional > Labels: ScenarioSimulation, drools-tools > > According a discussion [here|https://github.com/kiegroup/drools/pull/2630#discussion_r341188931] we should refactor the method _DOMParserUtil.createNodeAtPosition_ to simplify its usage by dropping its last parameter. This parameter is null in most cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4721) Use Objects.equals in ScesimModelDescriptor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4721?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4721: ------------------------------- Priority: Optional (was: Major) > Use Objects.equals in ScesimModelDescriptor > ------------------------------------------- > > Key: DROOLS-4721 > URL: https://issues.redhat.com/browse/DROOLS-4721 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Optional > Labels: ScenarioSimulation, drools-tools > > We should use _Objects.equals()_ instead of simple _equals_ in the [ScesimModelDescriptor|https://github.com/kiegroup/drools/blob/b1bc7ebb290...] class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4720) Use Objects.equals in AbstractScesimData

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4720?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4720: ------------------------------- Priority: Optional (was: Major) > Use Objects.equals in AbstractScesimData > ---------------------------------------- > > Key: DROOLS-4720 > URL: https://issues.redhat.com/browse/DROOLS-4720 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Optional > Labels: ScenarioSimulation, drools-tools > > We should use _Objects.equals()_ instead of simple _equals_ in the [AbstractScesimData|https://github.com/kiegroup/drools/blob/b1bc7ebb290604...] class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13340) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Stefano Maestri (Jira)

[ https://issues.redhat.com/browse/WFLY-13340?page=com.atlassian.jira.plugi... ] Stefano Maestri reassigned WFLY-13340: -------------------------------------- Assignee: Flavia Rainone (was: Stefano Maestri) > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: WFLY-13340 > URL: https://issues.redhat.com/browse/WFLY-13340 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Chao Wang > Assignee: Flavia Rainone > Priority: Critical > > By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 > There is a constant error in server shutdown > {code:xml} > 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) > 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13337) Upgrade CXF from 3.3.5 to 3.3.6 (Fixes CVE-2020-1954)

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13337?page=com.atlassian.jira.plugi... ] Jim Ma updated WFLY-13337: -------------------------- Security: (was: Red Hat Internal) > Upgrade CXF from 3.3.5 to 3.3.6 (Fixes CVE-2020-1954) > ----------------------------------------------------- > > Key: WFLY-13337 > URL: https://issues.redhat.com/browse/WFLY-13337 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Brian Stansberry > Assignee: Jim Ma > Priority: Major > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > https://nvd.nist.gov/vuln/detail/CVE-2020-1954 affects CXF 3.3.5; fixed in 3.3.6 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2464) Getting OutOfMemory Error

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2464?page=com.atlassian.jira.plugin... ] Bela Ban closed JGRP-2464. -------------------------- Resolution: Incomplete Description > Getting OutOfMemory Error > ------------------------- > > Key: JGRP-2464 > URL: https://issues.redhat.com/browse/JGRP-2464 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.13 > Reporter: Bhavesh Kharwa > Assignee: Bela Ban > Priority: Major > Attachments: oom-jgroup.jpg > > > I am using artemis version 2.11.0 and run artemis in master slave. There are two master and each master having slave. Please find attached screenshot of OutOfMemory error. > I have tried to reproduce this issue but not able to reproduce it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2464) Getting OutOfMemory Error

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2464?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2464: -------------------------------- Some process probably connected to this one and the first 4 (random) bytes read by this process were interpreted as length, such that the buffer allocation caused an OOME. I can't really diagnose anything with such little info. > Getting OutOfMemory Error > ------------------------- > > Key: JGRP-2464 > URL: https://issues.redhat.com/browse/JGRP-2464 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.13 > Reporter: Bhavesh Kharwa > Assignee: Bela Ban > Priority: Major > Attachments: oom-jgroup.jpg > > > I am using artemis version 2.11.0 and run artemis in master slave. There are two master and each master having slave. Please find attached screenshot of OutOfMemory error. > I have tried to reproduce this issue but not able to reproduce it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11905) Move module org.apache.xml-resolver from WildFly Core to WildFly

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-11905?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-11905: ------------------------------------- [~brian.stansberry] After our discussion on google chat I understood what things needs to be move, previously I was looking into other packs of wildfly. I have moved the module from wildfly-core to wildlfy. Thanks, Parul > Move module org.apache.xml-resolver from WildFly Core to WildFly > ---------------------------------------------------------------- > > Key: WFLY-11905 > URL: https://issues.redhat.com/browse/WFLY-11905 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Brian Stansberry > Assignee: Parul Sharma > Priority: Minor > > The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: > {code} > $ git grep xml-resolver | grep module.x > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> > {code} > Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13340) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown

by Chao Wang (Jira)

Chao Wang created WFLY-13340: -------------------------------- Summary: Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown Key: WFLY-13340 URL: https://issues.redhat.com/browse/WFLY-13340 Project: WildFly Issue Type: Bug Components: JCA Reporter: Chao Wang Assignee: Stefano Maestri By upgrading IJ to 1.4.21. Final https://issues.redhat.com/browse/WFLY-1324 There is a constant error in server shutdown {code:xml} 12:12:44,713 ERROR [stderr] (ConnectionValidator) Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:151) 12:12:44,714 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1261) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:457) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator$ConnectionValidatorRunner.run(ConnectionValidator.java:317) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 12:12:44,715 ERROR [stderr] (ConnectionValidator) at java.lang.Thread.run(Thread.java:748) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4882) Correct minOccurts value for host element in XSD

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-4882?page=com.atlassian.jira.plug... ] Chao Wang updated WFCORE-4882: ------------------------------ Steps to Reproduce: was: * Install a vanilla JBoss EAP 7.1.6 and a vanilla JBoss EAP 7.2.3 * On JBoss EAP 7.1.6 change the {{domain.xml}}/{{management}} configuration to this: {code:xml} <management> <access-control provider="simple"> <host-scoped-roles> <role name="custom-role-name" base-role="Administrator"> </role> </host-scoped-roles> <role-mapping> <role name="SuperUser"> <include> <user name="$local"/> </include> </role> </role-mapping> </access-control> </management> {code} * Run the migration {{$JBOSS_72_HOME/bin/jboss-server-migration.sh -s $JBOSS_71_HOME -t $JBOSS_72_HOME}} * Add an arbitrary management user to JBoss EAP 7.2.3 * Start JBoss EAP 7.2.3 server in domain mode and access the HAL {{http://localhost:9990}} > Correct minOccurts value for host element in XSD > ------------------------------------------------ > > Key: WFCORE-4882 > URL: https://issues.redhat.com/browse/WFCORE-4882 > Project: WildFly Core > Issue Type: Bug > Components: Management, Server > Affects Versions: 11.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > Attachments: Screenshot.png > > > Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL. > A broken domain configuration > {code:xml} > <host-scoped-roles> > <role name="custom-role-name" base-role="Administrator"> > </role> > </host-scoped-roles> > {code} > This broken configuration doesn't bother the old HAL, so user only see the issue from HAL after the migration. > The correct one should be: > {code:xml} > <host-scoped-roles> > <role name="dbaish" base-role="Administrator"> > <host name="master"/> > </role> > </host-scoped-roles> > {code} > https://github.com/wildfly/wildfly-core/blob/11.0.0.Final/server/src/main... show minOccurs="1", which is incorrect, the minOccurs should be 0 here. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020