June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4926) Upgrade WildFly Elytron from 1.11.3.Final to 1.11.4.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4926?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4926: ------------------------------------- Security: (was: Red Hat Internal) > Upgrade WildFly Elytron from 1.11.3.Final to 1.11.4.Final > --------------------------------------------------------- > > Key: WFCORE-4926 > URL: https://issues.redhat.com/browse/WFCORE-4926 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ilia Vassilev > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > Fix For: 12.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4928) Upgrade WildFly Elytron Web from 1.7.0.Final to 1.7.1.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4928?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4928: ------------------------------------- Security: (was: Red Hat Internal) > Upgrade WildFly Elytron Web from 1.7.0.Final to 1.7.1.Final > ----------------------------------------------------------- > > Key: WFCORE-4928 > URL: https://issues.redhat.com/browse/WFCORE-4928 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ilia Vassilev > Assignee: Darran Lofthouse > Priority: Major > Labels: downstream_dependency > Fix For: 12.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned WFCORE-4959: ---------------------------------------- Assignee: (was: Brian Stansberry) > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Joao Paulo Goncalves > Priority: Major > Labels: domain-mode > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4959: ------------------------------------- Component/s: Management > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Joao Paulo Goncalves > Assignee: Brian Stansberry > Priority: Major > Labels: domain-mode > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4959: ------------------------------------- Labels: domain-mode (was: ) > Feature for checking module installation in JBoss > ------------------------------------------------- > > Key: WFCORE-4959 > URL: https://issues.redhat.com/browse/WFCORE-4959 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Joao Paulo Goncalves > Assignee: Brian Stansberry > Priority: Major > Labels: domain-mode > > Using CLI tool or Administrative Console is not possible at this moment to check if a custom added module was added correctly, especially in domain mode. The only alternative available is to add host per host. This approach takes time, and for unused users there isn't some visual (GUI) to help them. > JBoss CLI approach: > module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add --source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts that belongs to the domain) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-13051: ---------------------------------------- [~nimo22] That method and feature is specific to the ScheduledThreadPoolExecutor, not the ScheduledExecutorService interface it implements. > provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService > ------------------------------------------------------------------ > > Key: WFLY-13051 > URL: https://issues.redhat.com/browse/WFLY-13051 > Project: WildFly > Issue Type: Enhancement > Components: Concurrency Utilities > Affects Versions: 19.0.0.Beta1 > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > Using > {code:java} > @Resource > private ManagedScheduledExecutorService executor; > {code} > provides no possiblity to setRemoveOnCancelPolicy to true. > A casting within a method: > {code:java} > ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); > {code} > throws the error: > {code:java} > Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) > {code} > Please provide option to cast or if not possible to add the property > {code:java} > setRemoveOnCancelPolicy() > {code} > within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] nimo stephan edited comment on WFLY-13051 at 6/1/20 2:52 PM: ------------------------------------------------------------- I thought that the _ManagedScheduledExecutorServiceAdapter_ can be casted to {code:java} ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); {code} because of {code:java} public interface ManagedScheduledExecutorService extends ManagedExecutorService, ScheduledExecutorService {code} {code:java} public class ScheduledThreadPoolExecutor extends ThreadPoolExecutor implements ScheduledExecutorService { {code} I see no reason why the user is not allowed to use _setRemoveOnCancelPolicy()_ on jee containers. Is there a way to make it possible to use "setRemoveOnCancelPolicy(true)" on the injected _ManagedScheduledExecutorService_ instance? was (Author: nimo22): I thought that the _ManagedScheduledExecutorServiceAdapter_ can be casted to {code:java} ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); {code} because of {code:java} public interface ManagedScheduledExecutorService extends ManagedExecutorService, ScheduledExecutorService {code} I see no reason why the user is not allowed to use _setRemoveOnCancelPolicy()_ on jee containers. Is there a way to make it possible to use "setRemoveOnCancelPolicy(true)" on the injected _ManagedScheduledExecutorService_ instance? > provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService > ------------------------------------------------------------------ > > Key: WFLY-13051 > URL: https://issues.redhat.com/browse/WFLY-13051 > Project: WildFly > Issue Type: Enhancement > Components: Concurrency Utilities > Affects Versions: 19.0.0.Beta1 > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > Using > {code:java} > @Resource > private ManagedScheduledExecutorService executor; > {code} > provides no possiblity to setRemoveOnCancelPolicy to true. > A casting within a method: > {code:java} > ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); > {code} > throws the error: > {code:java} > Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) > {code} > Please provide option to cast or if not possible to add the property > {code:java} > setRemoveOnCancelPolicy() > {code} > within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13051) provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/WFLY-13051?page=com.atlassian.jira.plugi... ] nimo stephan commented on WFLY-13051: ------------------------------------- I thought that the _ManagedScheduledExecutorServiceAdapter_ can be casted to {code:java} ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); {code} because of {code:java} public interface ManagedScheduledExecutorService extends ManagedExecutorService, ScheduledExecutorService {code} I see no reason why the user is not allowed to use _setRemoveOnCancelPolicy()_ on jee containers. Is there a way to make it possible to use "setRemoveOnCancelPolicy(true)" on the injected _ManagedScheduledExecutorService_ instance? > provide setRemoveOnCancelPolicy on ManagedScheduledExecutorService > ------------------------------------------------------------------ > > Key: WFLY-13051 > URL: https://issues.redhat.com/browse/WFLY-13051 > Project: WildFly > Issue Type: Enhancement > Components: Concurrency Utilities > Affects Versions: 19.0.0.Beta1 > Reporter: nimo stephan > Assignee: Eduardo Martins > Priority: Major > > Using > {code:java} > @Resource > private ManagedScheduledExecutorService executor; > {code} > provides no possiblity to setRemoveOnCancelPolicy to true. > A casting within a method: > {code:java} > ((ScheduledThreadPoolExecutor) executor).setRemoveOnCancelPolicy(true); > {code} > throws the error: > {code:java} > Caused by: javax.ejb.EJBException: java.lang.ClassCastException: class org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter cannot be cast to class java.util.concurrent.ScheduledThreadPoolExecutor (org.glassfish.enterprise.concurrent.ManagedScheduledExecutorServiceAdapter is in unnamed module of loader 'org.glassfish.javax.enterprise.concurrent' @a93b7af; java.util.concurrent.ScheduledThreadPoolExecutor is in module java.base of loader 'bootstrap') > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3@17.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) > {code} > Please provide option to cast or if not possible to add the property > {code:java} > setRemoveOnCancelPolicy() > {code} > within the object ManagedScheduledExecutorService. Because without it, we cannot remove a task from the queue with "future.cancel(false)". -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem

by Richard Achmatowicz (Jira)

[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ] Richard Achmatowicz commented on WFLY-13433: -------------------------------------------- Completed one of the more tricky resources, EJBRemoteResourceDefinition. See: https://github.com/rachmatowicz/wildfly/tree/WFLY-13433-remote > Improve capability support in EJB3 subsystem > -------------------------------------------- > > Key: WFLY-13433 > URL: https://issues.redhat.com/browse/WFLY-13433 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 20.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > > Survey all external subsystem dependencies and introduce capability based dependencies where required. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4916) Unclear attribute name completion for LIST type

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4916?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4916: ------------------------------------------ This seems like an enhancement. Prompting with both '[' and ',' would be better IMHO than completing with '['. The '[' is a valid option but it's not the only one and not even the most likely one. That said, I don't believe we complete with a ',' when people hit tab after other non-complex attribute names. If we start completing/prompting with a ',' in some cases it should be done in all cases. Which starts to get into the Enhancement territory. > Unclear attribute name completion for LIST type > ----------------------------------------------- > > Key: WFCORE-4916 > URL: https://issues.redhat.com/browse/WFCORE-4916 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 12.0.0.Beta1 > Reporter: Chao Wang > Assignee: Jean Francois Denise > Priority: Minor > > Following discussion in WFCORE-4908. There is a completion of "[" for LIST type attribute name after hitting tab, for example: > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options > {code} > added here https://github.com/wildfly/wildfly-core/blob/12.0.0.Beta1/cli/src/main/ja... > It seems to me that misleads to the wrong syntax as described in WFCORE-4908. > {code} > [domain@localhost:9990 /] /host=master/server-config=server-one/jvm=default:write-attribute(name=jvm-options[... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020