April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1959) Release WildFly Elytron 1.12.0.CR1

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1959?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved ELY-1959. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.12.0.CR1 > ---------------------------------- > > Key: ELY-1959 > URL: https://issues.redhat.com/browse/ELY-1959 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.12.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4953) Upgrade WildFly Elytron to 1.12.0.CR1

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4953: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.12.0.CR1 Key: WFCORE-4953 URL: https://issues.redhat.com/browse/WFCORE-4953 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 12.0.0.Beta3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13420) Enable Elytron mixed domain test suites

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13420: ------------------------------------------- Summary: Enable Elytron mixed domain test suites Key: WFLY-13420 URL: https://issues.redhat.com/browse/WFLY-13420 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Elytron mixed domain test suites were ignored by WFLY-8926 until WFCORE-2882 is integrated. Those test suites can be unignored now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5284) MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8

by Daniel Rosa (Jira)

[ https://issues.redhat.com/browse/DROOLS-5284?page=com.atlassian.jira.plug... ] Daniel Rosa updated DROOLS-5284: -------------------------------- Tester: Daniel Rosa > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > ---------------------------------------------------------- > > Key: DROOLS-5284 > URL: https://issues.redhat.com/browse/DROOLS-5284 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > MVELTest.testTypeCoercionLongDivByInt fails with IBM JDK 8 > {noformat} > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.97 s <<< FAILURE! - in org.drools.compiler.integrationtests.MVELTest > [ERROR] testTypeCoercionLongDivByInt(org.drools.compiler.integrationtests.MVELTest) Time elapsed: 0.962 s <<< FAILURE! > java.lang.AssertionError: expected:<7.350000> but was:<7> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.drools.compiler.integrationtests.MVELTest.testTypeCoercionLongDivByInt(MVELTest.java:1150) > ... > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] MVELTest.testTypeCoercionLongDivByInt:1150 expected:<7.350000> but was:<7> > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ELY-1959) Release WildFly Elytron 1.12.0.CR1

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1959: ------------------------------------- Summary: Release WildFly Elytron 1.12.0.CR1 Key: ELY-1959 URL: https://issues.redhat.com/browse/ELY-1959 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.12.0.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5285) Implement maven-dependency-plugin inside drools project

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5285?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5285: ------------------------------------- Involved: Daniele Zonca, Luca Molteni, Mario Fusco, Michael Anstis (was: Daniele Zonca, Luca Molteni, Michael Anstis) > Implement maven-dependency-plugin inside drools project > ------------------------------------------------------- > > Key: DROOLS-5285 > URL: https://issues.redhat.com/browse/DROOLS-5285 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools > > Replace the plugin currently used to check/enfore dependencies with the "maven-dependency-plugin" inside the "drools" project. > See drools-wb/pom.xml as configuration example -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-170) Release Remoting JMX 1.1.4.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/REMJMX-170?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved REMJMX-170. ------------------------------------- Resolution: Done > Release Remoting JMX 1.1.4.Final > -------------------------------- > > Key: REMJMX-170 > URL: https://issues.redhat.com/browse/REMJMX-170 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.1.4.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5285) Implement maven-dependency-plugin inside drools project

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5285: ---------------------------------------- Summary: Implement maven-dependency-plugin inside drools project Key: DROOLS-5285 URL: https://issues.redhat.com/browse/DROOLS-5285 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Replace the plugin currently used to check/enfore dependencies with the "maven-dependency-plugin" inside the "drools" project. See drools-wb/pom.xml as configuration example -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-170) Release Remoting JMX 1.1.4.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created REMJMX-170: --------------------------------------- Summary: Release Remoting JMX 1.1.4.Final Key: REMJMX-170 URL: https://issues.redhat.com/browse/REMJMX-170 Project: Remoting JMX Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.4.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-166) IllegalThreadStateException after idle jmx connection

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/REMJMX-166?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated REMJMX-166: ------------------------------------ Fix Version/s: 1.1.4.CR1 > IllegalThreadStateException after idle jmx connection > ----------------------------------------------------- > > Key: REMJMX-166 > URL: https://issues.redhat.com/browse/REMJMX-166 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 3.0.2.Final, 3.0.3.Final > Environment: org.jboss.remotingjmx:remoting-jmx:3.0.3.Final + java8 > Reporter: Märt Bakhoff > Assignee: Brad Maxwell > Priority: Blocker > Labels: downstream_dependency > Fix For: 1.1.4.CR1, 3.0.4.Final, 3.1.0.Beta1 > > Attachments: REMJMX-160.jar, REMJMX-166.jar > > > Start wildfly-17.0.1/bin/standalone.sh, then run this code snippet: > {noformat} > JMXServiceURL url = new JMXServiceURL("service:jmx:remote+http://127.0.0.1:9990"); > try (JMXConnector connector = new RemotingConnectorProvider().newJMXConnector(url, Collections.emptyMap())) { > connector.connect(); > MBeanServerConnection beanServer = connector.getMBeanServerConnection(); > RuntimeMXBean bean = ManagementFactory.newPlatformMXBeanProxy(beanServer, ManagementFactory.RUNTIME_MXBEAN_NAME, RuntimeMXBean.class); > Thread.sleep(70_000); > System.out.println("uptime: " + bean.getUptime()); > } > {noformat} > The following exception is always thrown: > {noformat} > Exception in thread "XNIO-1 task-12" java.lang.IllegalThreadStateException > at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) > at java.lang.Thread.init(Thread.java:405) > at java.lang.Thread.init(Thread.java:349) > at java.lang.Thread.<init>(Thread.java:599) > at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager$1.newThread(ClientExecutorManager.java:56) > at java.util.concurrent.ThreadPoolExecutor$Worker.<init>(ThreadPoolExecutor.java:619) > at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:932) > at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1378) > at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.execute(ClientExecutorManager.java:64) > at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver.handleMessage(ClientCommon.java:118) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} > The cause is in org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.<init>. It creates a thread pool with Executors.newCachedThreadPool that has the default keepAliveTime of 60s. > The thread factory is using a daemon thread group REMOTING_JMX that will self-destruct when the cached thread is terminated. > The same code works when using older org.jboss.remotingjmx:remoting-jmx:3.0.1.Final. The regression is likely caused by commit https://github.com/jbossas/remoting-jmx/commit/2d6ae6c26da43304b752fc48f1... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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