February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11672) @ApplicationScoped does not work when used with @ServerEndpoint

by Marek Marusic (Jira)

Marek Marusic created WFLY-11672: ------------------------------------ Summary: @ApplicationScoped does not work when used with @ServerEndpoint Key: WFLY-11672 URL: https://issues.jboss.org/browse/WFLY-11672 Project: WildFly Issue Type: Bug Components: CDI / Weld, Web Sockets Affects Versions: 15.0.1.Final Reporter: Marek Marusic Assignee: Matej Novotny When the @ApplicationScoped annotation is used in combination with @ServerEndpoint the class is instantiated on every new connection instead of being instantiated once for the whole application. The expected behaviour: There should be only one instance of the class which is annotated with @ApplicationScoped and @ServerEndpoint annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3906) Upgrade JBoss Modules to 1.8.6.Final

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-3906?page=com.atlassian.jira.plugi... ] Marek Kopecký edited comment on WFCORE-3906 at 2/5/19 5:59 AM: --------------------------------------------------------------- [~dmlloyd], [~ropalka] (cc [~mjurc]) Do you have some plans about MODULES-372 and JBoss Modules 1.10 in WF and WF-Core? was (Author: mkopecky): [~dmlloyd], [~ropalka] Do you have some plans about MODULES-372 and JBoss Modules 1.10 in WF and WF-Core? > Upgrade JBoss Modules to 1.8.6.Final > ------------------------------------ > > Key: WFCORE-3906 > URL: https://issues.jboss.org/browse/WFCORE-3906 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: David Lloyd > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3906) Upgrade JBoss Modules to 1.8.6.Final

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-3906?page=com.atlassian.jira.plugi... ] Marek Kopecký commented on WFCORE-3906: --------------------------------------- [~dmlloyd], [~ropalka] Do you have some plans about MODULES-372 and JBoss Modules 1.10 in WF and WF-Core? > Upgrade JBoss Modules to 1.8.6.Final > ------------------------------------ > > Key: WFCORE-3906 > URL: https://issues.jboss.org/browse/WFCORE-3906 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: David Lloyd > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ] Bartosz Baranowski resolved WFLY-10268. --------------------------------------- Resolution: Cannot Reproduce > TimerService sometimes doesn't invoke timers > -------------------------------------------- > > Key: WFLY-10268 > URL: https://issues.jboss.org/browse/WFLY-10268 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Bartosz Baranowski > Priority: Major > Attachments: WFLY-10268-reproducer.patch > > > The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked. > Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately). > Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-10268: ------------------------------------------- Unfortunately Im unable to reproduce - though, given latency I thought I could. Given spam it takes timers to invoker EJB, still all of them come through. If you can isolate reproducer please reopen. > TimerService sometimes doesn't invoke timers > -------------------------------------------- > > Key: WFLY-10268 > URL: https://issues.jboss.org/browse/WFLY-10268 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Bartosz Baranowski > Priority: Major > Attachments: WFLY-10268-reproducer.patch > > > The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked. > Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately). > Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-10268: -------------------------------------- Attachment: WFLY-10268-reproducer.patch > TimerService sometimes doesn't invoke timers > -------------------------------------------- > > Key: WFLY-10268 > URL: https://issues.jboss.org/browse/WFLY-10268 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Bartosz Baranowski > Priority: Major > Attachments: WFLY-10268-reproducer.patch > > > The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked. > Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately). > Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-2262: --------------------------------------- [~jomarko] [~manstis] That ticket is intended to improve full page width for canvas grid component so it is not directly related to this one. Btw we need to add persistence of column size for sure also in Test Scenario so let me know if the way are you using to implement this can be reused > [DMN Designer] DRD Grid Column width is not preserved > ----------------------------------------------------- > > Key: DROOLS-2262 > URL: https://issues.jboss.org/browse/DROOLS-2262 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DND Grid Column don't preserve the width. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-10268: -------------------------------------- Attachment: (was: WFLY-10268-reproducer.patch) > TimerService sometimes doesn't invoke timers > -------------------------------------------- > > Key: WFLY-10268 > URL: https://issues.jboss.org/browse/WFLY-10268 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Rich DiCroce > Assignee: Bartosz Baranowski > Priority: Major > > The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked. > Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately). > Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2262: ------------------------------------- [~manstis] HI, just wanted to bring to your attention DROOLS-3377 that seems very similar to me, maybe you could get in touch with [~danielezonca] to check if work is not duplicated. > [DMN Designer] DRD Grid Column width is not preserved > ----------------------------------------------------- > > Key: DROOLS-2262 > URL: https://issues.jboss.org/browse/DROOLS-2262 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DND Grid Column don't preserve the width. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11629) Transaction service isn't available when dynamically adding transactional annotation

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-11629?page=com.atlassian.jira.plugin... ] Ondra Chaloupka commented on WFLY-11629: ---------------------------------------- [~juagonza] I see your point. First I would argue that by deploying to different containers you need to apply some of their habits. The class loading in WildFly is based on modules. If you mind changing the {{META-INF}} you can still use the descriptor {{jboss-deployment-structure.xml}} to get the same. I understand the argument that same example works for Paraya. From the implementation perspective I don't like the need of adding the JTS modules to dependency even if it's not necessary. By me the benefit of current behaviour is that the dependency is not forced up to time it's needed by the application (which declares {{@Transactional}} annotation). I think there are still some trade-offs which need to be done. For sure this behaviour should be documented. > Transaction service isn't available when dynamically adding transactional annotation > ------------------------------------------------------------------------------------ > > Key: WFLY-11629 > URL: https://issues.jboss.org/browse/WFLY-11629 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 15.0.1.Final > Reporter: Juan Gonzalez > Assignee: Ondra Chaloupka > Priority: Major > Attachments: wildfly_dynamic_tx_reproducer.zip > > > When adding dynamically a transactional annotation, transactional module isn't loaded, so transactions aren't available and throws this error: > {noformat} > javax.persistence.TransactionRequiredException: WFLYJPA0060: Transaction is required to perform this operation (either use a transaction or extended persistence context) > {noformat} > I've attached a reproducer with a test in order to reproduce this. There you can see that there is a CDI producer that dynamically adds the annotation for transactions, that doesn't work. > [~mkouba] found this could be an optimization for not loading JTS module: https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... > In order to execute tests: > mvn clean test > To execute test, passing in Payara: > mvn clean test -Ppayara -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 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 February 2019