April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2401) Version number for configuration

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2401?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2401. ---------------------------- Resolution: Done Fixed in master and backported to 4.x > Version number for configuration > -------------------------------- > > Key: JGRP-2401 > URL: https://issues.redhat.com/browse/JGRP-2401 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > Add a version to the config, which corresponds with the JGroups version. > At startup, if the JGroups version and the config version don't match, issue a warning. Possibly don't start if the major version differs. > Example: > {code:xml} > <config xmlns="urn:org:jgroups" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd" > version="5.0.0.Final"> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5228) Multiple Topic reassignment on updated status node

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5228?page=com.atlassian.jira.plug... ] Massimiliano Dessi commented on DROOLS-5228: -------------------------------------------- https://github.com/kiegroup/droolsjbpm-integration/pull/2060 https://github.com/kiegroup/openshift-drools-hacep/pull/88 > Multiple Topic reassignment on updated status node > -------------------------------------------------- > > Key: DROOLS-5228 > URL: https://issues.redhat.com/browse/DROOLS-5228 > Project: Drools > Issue Type: Bug > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1403) Make connection Validation (at ConnectionValidator) outside of lock

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/JBJCA-1403?page=com.atlassian.jira.plugi... ] Flavia Rainone resolved JBJCA-1403. ----------------------------------- Resolution: Done > Make connection Validation (at ConnectionValidator) outside of lock > ------------------------------------------------------------------- > > Key: JBJCA-1403 > URL: https://issues.redhat.com/browse/JBJCA-1403 > Project: IronJacamar > Issue Type: Enhancement > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > As can be seen in the following stack trace, connection validation inside the connection validator lock might lock the entire prefill of other pools: > {code} > "default task-1122" #4743 prio=5 os_prio=0 tid=0x000000000929f800 nid=0x12067 waiting for monitor entry [0x00007fe6c7305000] > java.lang.Thread.State: BLOCKED (on object monitor) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getManagedConnectionPool(AbstractPool.java:299) > - waiting to lock <0x0000000083be8028> (a org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:596) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624) > at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789) > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151) > at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64) > ... > "default task-1144" #4839 prio=5 os_prio=0 tid=0x000000000ccca800 nid=0x12718 waiting on condition [0x00007fe6cc532000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x000000008082b8f8> (a java.util.concurrent.locks.ReentrantLock$FairSync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) > at java.util.concurrent.locks.ReentrantLock$FairSync.lock(ReentrantLock.java:224) > at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) > at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator.internalRegisterPool(ConnectionValidator.java:185) > at org.jboss.jca.core.connectionmanager.pool.validator.ConnectionValidator.registerPool(ConnectionValidator.java:167) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.initialize(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:196) > at org.jboss.jca.core.connectionmanager.pool.mcp.ManagedConnectionPoolFactory.init(ManagedConnectionPoolFactory.java:191) > at org.jboss.jca.core.connectionmanager.pool.mcp.ManagedConnectionPoolFactory.create(ManagedConnectionPoolFactory.java:173) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getManagedConnectionPool(AbstractPool.java:306) > - locked <0x0000000083be8028> (a org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:596) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624) > at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789) > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151) > at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64) > {code} > The reason for this is that a new pool must be registered, and currently this operation is being blocked by connection validation. If connection validation is slow, this could compromise other threads creating pools and connections as shown in the example. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

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

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/JBJCA-1407?page=com.atlassian.jira.plugi... ] Flavia Rainone resolved JBJCA-1407. ----------------------------------- Resolution: Done > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1407 > URL: https://issues.redhat.com/browse/JBJCA-1407 > Project: IronJacamar > Issue Type: Bug > 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)

4 years, 7 months

1
0
0 / 0

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

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/JBJCA-1407?page=com.atlassian.jira.plugi... ] Flavia Rainone commented on JBJCA-1407: --------------------------------------- Thanks for the fix, [~brian.stansberry]! > Exception in thread "ConnectionValidator" java.lang.IllegalMonitorStateException in server shutdown > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1407 > URL: https://issues.redhat.com/browse/JBJCA-1407 > Project: IronJacamar > Issue Type: Bug > 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)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1415) Move away from expensive enum switch

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-1415?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-1415: ---------------------------------------- I don't think my comments stand as much about the topic branches but I think the general pattern for parsing has changed a lot over the last five years so a lot of the newer code shouldn't be as affected by this. > Move away from expensive enum switch > ------------------------------------ > > Key: WFLY-1415 > URL: https://issues.redhat.com/browse/WFLY-1415 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Priority: Minor > Labels: janitor > > We use enums and enum switch extensively. These constructs generate many, many additional classes and bloat the code base unnecessarily. > All cases where we are using enum-based switches for our XML parsers should be converted to use Java 7 String switch instead. The enum values shall be replaced with String constant fields, all enum switches converted to String switches, and all enum types removed from these classes. The net result should be a reduction by dozens if not hundreds of .class files, and possibly a measurable performance boost as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4910) Log WARN if JBoss Logging Handler gets removed

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFCORE-4910?page=com.atlassian.jira.plug... ] Bartosz Baranowski reassigned WFCORE-4910: ------------------------------------------ Assignee: James Perkins (was: Bartosz Baranowski) > Log WARN if JBoss Logging Handler gets removed > ----------------------------------------------- > > Key: WFCORE-4910 > URL: https://issues.redhat.com/browse/WFCORE-4910 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: James Perkins > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5228) Multiple Topic reassignment on updated status node

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-5228: ------------------------------------------ Summary: Multiple Topic reassignment on updated status node Key: DROOLS-5228 URL: https://issues.redhat.com/browse/DROOLS-5228 Project: Drools Issue Type: Bug Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13292) Upgrade FasterXML from 2.10.1 to 2.10.3

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13292?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13292: ------------------------------ Labels: downstream_dependency (was: ) > Upgrade FasterXML from 2.10.1 to 2.10.3 > --------------------------------------- > > Key: WFLY-13292 > URL: https://issues.redhat.com/browse/WFLY-13292 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Bartosz Baranowski > Assignee: Alessio Soldano > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4910) Log WARN if JBoss Logging Handler gets removed

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFCORE-4910?page=com.atlassian.jira.plug... ] Bartosz Baranowski updated WFCORE-4910: --------------------------------------- Component/s: Logging > Log WARN if JBoss Logging Handler gets removed > ----------------------------------------------- > > Key: WFCORE-4910 > URL: https://issues.redhat.com/browse/WFCORE-4910 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

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