April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2405) Re-activate Channel

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2405?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2405: -------------------------------- This is a huge change, not sure it's really needed. Like {{ForkChannel}}, a new channel impl could extend {{JChannel}} rather than implement {{Channel}}. > Re-activate Channel > ------------------- > > Key: JGRP-2405 > URL: https://issues.redhat.com/browse/JGRP-2405 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0.0.Alpha5 > > > The {{Channel}} interface has been deprecated. However, to implement JGraSS [1], we need it. Remove the @Deprecated tag and make JChannel implement Channel. > [1] https://issues.jboss.org/browse/JGRP-2411 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13391) getContextClassLoader is null in Managed thread factory

by Dheeraj Joshi (Jira)

[ https://issues.redhat.com/browse/WFLY-13391?page=com.atlassian.jira.plugi... ] Dheeraj Joshi commented on WFLY-13391: -------------------------------------- [~brian.stansberry] Adding {code:java} context-service="default" {code} in managed-executor-service makes it work as expected. [~emmartins] We are not setting any priorities for thread. However we are having few managed-thread-factory in xml configuration. Are you suggesting we could simply have one default managed-thread-factory and use it for all managed-executor-service? > getContextClassLoader is null in Managed thread factory > ------------------------------------------------------- > > Key: WFLY-13391 > URL: https://issues.redhat.com/browse/WFLY-13391 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Dheeraj Joshi > Assignee: Eduardo Martins > Priority: Major > Attachments: WildFly-16-server.log, WildFly-17-server.log, WildFly-18-server.log > > > We are using managed-thread-factory and Threads belong to this do not have context class loader associated with it > {code:java} > <managed-thread-factories> > <managed-thread-factory name="FlowWorkManagerThreadFactory" jndi-name="java:jboss/ee/concurrency/factory/FlowWorkManagerThreadFactory" context-service="default"/> > </managed-thread-factories> > <managed-executor-services> > <managed-executor-service > name="InteractiveWorkflowWorkManagerExecutorService" > jndi-name="java:jboss/ee/concurrency/executor/FLOW_MANAGEDEXECUTOR" > core-threads="${threadpool.interactiveWorkflow.minthread}" > max-threads="${threadpool.interactiveWorkflow.maxthread}" keepalive-time="5000" > queue-length="${threadpool.interactiveWorkflow.queuesize}" > thread-factory="FlowWorkManagerThreadFactory" > hung-task-threshold="600000" /> > </managed-executor-services> > {code} > classLoader variable in below code > {code:java} > final ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > {code} > evaluates as null when called inside managed thread. > Same code works fine with {{Wildfly 16}} and {{Wildfly 17.0.1}} > In 16 and 17.0.1 The class loader is from Service module loader. > Server logs with {{org.jboss.as.ee}} in {{TRACE}} level for {{Wildfly 16, 17.0.1 and 18}} are attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1129) Automate Masthead status

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1129?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1129: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/280 > Automate Masthead status > ------------------------ > > Key: SWSQE-1129 > URL: https://issues.redhat.com/browse/SWSQE-1129 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1733 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1122) UPI provisioning not working for OCP 4.4

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1122?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1122. ---------------------------------- Resolution: Done Added workaround for - https://bugzilla.redhat.com/show_bug.cgi?id=1811221 > UPI provisioning not working for OCP 4.4 > ---------------------------------------- > > Key: SWSQE-1122 > URL: https://issues.redhat.com/browse/SWSQE-1122 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > This job is failing for OCP 4.4 - https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13391) getContextClassLoader is null in Managed thread factory

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13391?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-13391: ---------------------------------------- [~dheerajjoshim] btw, the *thread-factory* attribute was deprecated by WFLY-12520, in case you want a non standard thread priority you should use instead the new *thread-priority* attribute. > getContextClassLoader is null in Managed thread factory > ------------------------------------------------------- > > Key: WFLY-13391 > URL: https://issues.redhat.com/browse/WFLY-13391 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Dheeraj Joshi > Assignee: Eduardo Martins > Priority: Major > Attachments: WildFly-16-server.log, WildFly-17-server.log, WildFly-18-server.log > > > We are using managed-thread-factory and Threads belong to this do not have context class loader associated with it > {code:java} > <managed-thread-factories> > <managed-thread-factory name="FlowWorkManagerThreadFactory" jndi-name="java:jboss/ee/concurrency/factory/FlowWorkManagerThreadFactory" context-service="default"/> > </managed-thread-factories> > <managed-executor-services> > <managed-executor-service > name="InteractiveWorkflowWorkManagerExecutorService" > jndi-name="java:jboss/ee/concurrency/executor/FLOW_MANAGEDEXECUTOR" > core-threads="${threadpool.interactiveWorkflow.minthread}" > max-threads="${threadpool.interactiveWorkflow.maxthread}" keepalive-time="5000" > queue-length="${threadpool.interactiveWorkflow.queuesize}" > thread-factory="FlowWorkManagerThreadFactory" > hung-task-threshold="600000" /> > </managed-executor-services> > {code} > classLoader variable in below code > {code:java} > final ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > {code} > evaluates as null when called inside managed thread. > Same code works fine with {{Wildfly 16}} and {{Wildfly 17.0.1}} > In 16 and 17.0.1 The class loader is from Service module loader. > Server logs with {{org.jboss.as.ee}} in {{TRACE}} level for {{Wildfly 16, 17.0.1 and 18}} are attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13391) getContextClassLoader is null in Managed thread factory

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13391?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-13391: ---------------------------------------- [~dheerajjoshim] we had a classloader leak that we fixed at https://issues.redhat.com/browse/WFLY-12384 , and part of the fix was to ensure executors use a thread factory without context service, which should be defined instead by the executor (as Brian suggested) > getContextClassLoader is null in Managed thread factory > ------------------------------------------------------- > > Key: WFLY-13391 > URL: https://issues.redhat.com/browse/WFLY-13391 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Dheeraj Joshi > Assignee: Eduardo Martins > Priority: Major > Attachments: WildFly-16-server.log, WildFly-17-server.log, WildFly-18-server.log > > > We are using managed-thread-factory and Threads belong to this do not have context class loader associated with it > {code:java} > <managed-thread-factories> > <managed-thread-factory name="FlowWorkManagerThreadFactory" jndi-name="java:jboss/ee/concurrency/factory/FlowWorkManagerThreadFactory" context-service="default"/> > </managed-thread-factories> > <managed-executor-services> > <managed-executor-service > name="InteractiveWorkflowWorkManagerExecutorService" > jndi-name="java:jboss/ee/concurrency/executor/FLOW_MANAGEDEXECUTOR" > core-threads="${threadpool.interactiveWorkflow.minthread}" > max-threads="${threadpool.interactiveWorkflow.maxthread}" keepalive-time="5000" > queue-length="${threadpool.interactiveWorkflow.queuesize}" > thread-factory="FlowWorkManagerThreadFactory" > hung-task-threshold="600000" /> > </managed-executor-services> > {code} > classLoader variable in below code > {code:java} > final ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > {code} > evaluates as null when called inside managed thread. > Same code works fine with {{Wildfly 16}} and {{Wildfly 17.0.1}} > In 16 and 17.0.1 The class loader is from Service module loader. > Server logs with {{org.jboss.as.ee}} in {{TRACE}} level for {{Wildfly 16, 17.0.1 and 18}} are attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13394) Release org.jboss.universe.producer:wildfly-producers:1.2.0.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13394: --------------------------------------- Summary: Release org.jboss.universe.producer:wildfly-producers:1.2.0.Final Key: WFLY-13394 URL: https://issues.redhat.com/browse/WFLY-13394 Project: WildFly Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Pick up https://github.com/wildfly/wildfly-producers/issues/11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13394) Release org.jboss.universe.producer:wildfly-producers:1.2.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13394?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13394: ------------------------------------ Fix Version/s: 19.1.0.Final > Release org.jboss.universe.producer:wildfly-producers:1.2.0.Final > ----------------------------------------------------------------- > > Key: WFLY-13394 > URL: https://issues.redhat.com/browse/WFLY-13394 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 19.1.0.Final > > > Pick up https://github.com/wildfly/wildfly-producers/issues/11 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13391) getContextClassLoader is null in Managed thread factory

by Dheeraj Joshi (Jira)

[ https://issues.redhat.com/browse/WFLY-13391?page=com.atlassian.jira.plugi... ] Dheeraj Joshi commented on WFLY-13391: -------------------------------------- I will test this and report. > getContextClassLoader is null in Managed thread factory > ------------------------------------------------------- > > Key: WFLY-13391 > URL: https://issues.redhat.com/browse/WFLY-13391 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 18.0.1.Final, 19.0.0.Final > Reporter: Dheeraj Joshi > Assignee: Eduardo Martins > Priority: Major > Attachments: WildFly-16-server.log, WildFly-17-server.log, WildFly-18-server.log > > > We are using managed-thread-factory and Threads belong to this do not have context class loader associated with it > {code:java} > <managed-thread-factories> > <managed-thread-factory name="FlowWorkManagerThreadFactory" jndi-name="java:jboss/ee/concurrency/factory/FlowWorkManagerThreadFactory" context-service="default"/> > </managed-thread-factories> > <managed-executor-services> > <managed-executor-service > name="InteractiveWorkflowWorkManagerExecutorService" > jndi-name="java:jboss/ee/concurrency/executor/FLOW_MANAGEDEXECUTOR" > core-threads="${threadpool.interactiveWorkflow.minthread}" > max-threads="${threadpool.interactiveWorkflow.maxthread}" keepalive-time="5000" > queue-length="${threadpool.interactiveWorkflow.queuesize}" > thread-factory="FlowWorkManagerThreadFactory" > hung-task-threshold="600000" /> > </managed-executor-services> > {code} > classLoader variable in below code > {code:java} > final ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > {code} > evaluates as null when called inside managed thread. > Same code works fine with {{Wildfly 16}} and {{Wildfly 17.0.1}} > In 16 and 17.0.1 The class loader is from Service module loader. > Server logs with {{org.jboss.as.ee}} in {{TRACE}} level for {{Wildfly 16, 17.0.1 and 18}} are attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4936) When server is started at suspend mode, :shutdown does not trigger a shutdown

by Chao Wang (Jira)

Chao Wang created WFCORE-4936: --------------------------------- Summary: When server is started at suspend mode, :shutdown does not trigger a shutdown Key: WFCORE-4936 URL: https://issues.redhat.com/browse/WFCORE-4936 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 12.0.0.Beta1 Reporter: Chao Wang Assignee: Chao Wang If server is started in suspend mode, :shutdown via cli does not trigger a shutdown; if I run :resume first then :shutdown, then it works. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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