January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-7841: ------------------------------------ Well, it makes sense. However, we should be careful here. bq. Tasks that are submitted to a managed instance of ExecutorService may still be running after the lifecycle of the submitting component. (2.3.2.1 Tasks and Contexts and Dependency Injection) If you submit a task which is a client proxy of a {{@RequestScoped}} bean, then the real bean instance executed will be (most probably) a completely different object than the one a user might think he/she is passing. This might be really confusing. So I think it's ok to activate request context and use {{@RequestScoped}} beans during task execution but the task itself should not be {{@RequestScoped}}. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-7841: -------------------------------------- I think we should probably do it as a non standard extension. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tomas Remes commented on WFLY-7841: ----------------------------------- Yes request scope is not active in this case and unfortunately it's not required by the Concurrency utilities spec AFAIK. Application scope should work. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2023) Log viewer does not show any log file for rpm installation

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2023?page=com.atlassian.jira.plugi... ] Bartosz Baranowski updated WFCORE-2023: --------------------------------------- Summary: Log viewer does not show any log file for rpm installation (was: (7.0.z) Log viewer does not show any log file for rpm installation) > Log viewer does not show any log file for rpm installation > ---------------------------------------------------------- > > Key: WFCORE-2023 > URL: https://issues.jboss.org/browse/WFCORE-2023 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: James Perkins > Fix For: 3.0.0.Alpha17 > > > I'm running a fresh RHEL7.3 server subscribed to the current jboss eap7 repository [1] using the rpm package. [2] > [1] subscription-manager repos --enable=jb-eap-7-for-rhel-RHEL_VERSION-server-rpms > [2] https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7544) @Startup @Singleton fails to invoke EJB via Remote interface in PostConstruct

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7544?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7544: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1389428|https://bugzilla.redhat.com/show_bug.cgi?id=1389428] from ON_QA to VERIFIED > @Startup @Singleton fails to invoke EJB via Remote interface in PostConstruct > ----------------------------------------------------------------------------- > > Key: WFLY-7544 > URL: https://issues.jboss.org/browse/WFLY-7544 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency > Fix For: 11.0.0.Alpha1 > > > While cross-vm calls to beans through remote interfaces while their @PostConstruct is not done yet should be disallowed, in-vm calls should be able to proceed normally. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7846) jboss-web.xml overlay option not honored

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-7846?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated WFLY-7846: ------------------------------- Summary: jboss-web.xml overlay option not honored (was: jboss-web.xml overlay option not honroed) > jboss-web.xml overlay option not honored > ---------------------------------------- > > Key: WFLY-7846 > URL: https://issues.jboss.org/browse/WFLY-7846 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Brad Maxwell > Assignee: Stuart Douglas > > The overlay option in jboss-web_10_0.xsd not honored: > {code} > The overlay element specifies additional static files overlays for this > web application. The content of the element should be a folder in the > filesystem containing the static files that will overlay the webapp's > static files, similar to what happens with regular JAR overlays. > {code} > {code} > <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" > version="10.0"> > <overlay>/home/web/content</overlay> > </jboss-web> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-7841: -------------------------------------- It sounds like the issue is that no request scope is set up for ManagedExecutorService tasks. I am not sure if this is required by spec, but it would make sense. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-7841: ------------------------------- Git Pull Request: (was: https://github.com/Tibor17/issue-7841) > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7847) [GSS](7.1.0) jboss-web.xml overlay option not honroed

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7847: ---------------------------------- Summary: [GSS](7.1.0) jboss-web.xml overlay option not honroed Key: WFLY-7847 URL: https://issues.jboss.org/browse/WFLY-7847 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Stuart Douglas The overlay option in jboss-web_10_0.xsd not honored: {code} The overlay element specifies additional static files overlays for this web application. The content of the element should be a folder in the filesystem containing the static files that will overlay the webapp's static files, similar to what happens with regular JAR overlays. {code} {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" version="10.0"> <overlay>/home/web/content</overlay> </jboss-web> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7846) jboss-web.xml overlay option not honroed

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-7846: ---------------------------------- Summary: jboss-web.xml overlay option not honroed Key: WFLY-7846 URL: https://issues.jboss.org/browse/WFLY-7846 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Reporter: Brad Maxwell Assignee: Stuart Douglas The overlay option in jboss-web_10_0.xsd not honored: {code} The overlay element specifies additional static files overlays for this web application. The content of the element should be a folder in the filesystem containing the static files that will overlay the webapp's static files, similar to what happens with regular JAR overlays. {code} {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_10_0.xsd" version="10.0"> <overlay>/home/web/content</overlay> </jboss-web> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 January 2017