June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-13424: ------------------------------------ that's what should be done then: if ee got an alias, it should resolve the alias until it got the actual value. I don't think that requiring that the default JMS ConnectionFactory MUST be the first JNDI entries is correct. > External pooled connection factory won't be properly injected if it has several JNDI entries > -------------------------------------------------------------------------------------------- > > Key: WFLY-13424 > URL: https://issues.redhat.com/browse/WFLY-13424 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 20.0.0.Beta1 > > > If the default JNDI name for MDB to get the resource adapter is not the first entry of the JNDI names bound for a pooled-connection-factory then the injection fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13424: ------------------------------------------ because when you are using an alias you don't get the value directly when resolving so you need to resolve again to obtain the proper value. > External pooled connection factory won't be properly injected if it has several JNDI entries > -------------------------------------------------------------------------------------------- > > Key: WFLY-13424 > URL: https://issues.redhat.com/browse/WFLY-13424 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 20.0.0.Beta1 > > > If the default JNDI name for MDB to get the resource adapter is not the first entry of the JNDI names bound for a pooled-connection-factory then the injection fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13424) External pooled connection factory won't be properly injected if it has several JNDI entries

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-13424?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-13424: ------------------------------------ I don't understand why the order of entries is now significant. As long as the JMS ConnectionFactory is properly bound in JNDI, it should be resolved by the `ee` subsystem to provide the default JMS ConnectionFactory (whether it's a direct JNDI entry or an alias) > External pooled connection factory won't be properly injected if it has several JNDI entries > -------------------------------------------------------------------------------------------- > > Key: WFLY-13424 > URL: https://issues.redhat.com/browse/WFLY-13424 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.1.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 20.0.0.Beta1 > > > If the default JNDI name for MDB to get the resource adapter is not the first entry of the JNDI names bound for a pooled-connection-factory then the injection fails. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugi... ] Flavia Rainone commented on WFLY-13514: --------------------------------------- This issue should be fixed by WFCORE-4988. > Huge memory leak in WildFly > --------------------------- > > Key: WFLY-13514 > URL: https://issues.redhat.com/browse/WFLY-13514 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF, Web (Undertow) > Affects Versions: 18.0.1.Final, 19.1.0.Final, 20.0.0.Beta1 > Reporter: Konrad Bak > Assignee: Flavia Rainone > Priority: Blocker > Fix For: 20.0.0.Final > > > https://github.com/konbk/bug-report-wildfly-oome > The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours. > When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 closed WFLY-13051. ---------------------------------- Resolution: Won't Do > 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, 11 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] sorry, it's not possible, and after internal team discussion we agreed allowing apps to reach internal executors would lock us on implementation details and could introduce other issues (e.g. security). If you really need to remove tasks when canceled (instead of when these expire) the work around possible would be for your app or custom extension to manage a ScheduledThreadPoolExecutor and use the ContextService to make tasks contextual (if needed). Not sure such workaround would have a significant performance advantage tho... > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3685: ------------------------------------ Attachment: columns2.png > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, columns.png, columns2.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-3685: ----------------------------------------- [~jomarko], they must be different. Input clauses support FEEL expressions, and on output columns we're able to achieve just two levels of depth with data type fields. Thus [~vpellegr] is generating columns accordingly: !columns.png|width=600! > [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3685 > URL: https://issues.redhat.com/browse/DROOLS-3685 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: 2020-05-21-14.57.31.gif, columns.png, columns.png, data-types.png, license.dmn > > > When creating a decision table, output clauses columns should be created based on the type of the output node. > This is what we are already doing for the input columns, that are created based on the type of the input node. > h3. Acceptance criteria > - Output ref is a simple built in type > - Output ref is simple but custom type > - Output ref is a structure with simple type fields > - Output ref is structure with custom type type fields > The flow for the input columns is described in the GIF below: > !2020-05-21-14.57.31.gif|height=450,width=950! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5396) Undo and Redo keyboard shortcuts do not work in grid editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5396?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5396: -------------------------------- Priority: Minor (was: Major) > Undo and Redo keyboard shortcuts do not work in grid editor > ----------------------------------------------------------- > > Key: DROOLS-5396 > URL: https://issues.redhat.com/browse/DROOLS-5396 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.39.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > We have these shortcuts in DMN designer > - Undo Ctrl+Z > - Redo Ctrl+Shift+Z > They work fine on graph editor. However they do not work in grid editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5396) Undo and Redo keyboard shortcuts do not work in grid editor

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5396: ----------------------------------- Summary: Undo and Redo keyboard shortcuts do not work in grid editor Key: DROOLS-5396 URL: https://issues.redhat.com/browse/DROOLS-5396 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.39.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes We have these shortcuts in DMN designer - Undo Ctrl+Z - Redo Ctrl+Shift+Z They work fine on graph editor. However they do not work in grid editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 June 2020