November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11233) allow EntityManager caching in the JPA container

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11233?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-11233: -------------------------------- Issue Type: Feature Request (was: Enhancement) > allow EntityManager caching in the JPA container > ------------------------------------------------ > > Key: WFLY-11233 > URL: https://issues.jboss.org/browse/WFLY-11233 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > > It could be interesting to see if caching EntityManager instances (per EntityManagerFactory) could improve performance for applications, that could benefit from that. > The JPA 2.2 specification mentions the below, pay particular attention to the text "whether entity manager instances are sometimes reused" in section 7.8.2, also look at mention of [88]: > {quote} > 7.8 Requirements on the Container > 7.8.1 Application-managed Persistence Contexts > When application-managed persistence contexts are used, the container must instantiate the entity manager factory and expose it to the application via JNDI. The container might use internal APIs to create the entity manager factory, or it might use the PersistenceProvider.createContainerEntityManagerFactory method. However, the container is required to support third-party persistence providers, and in this case the container must use the PersistenceProvider.createContainerEntityManagerFactory method to create the entity manager factory and the EntityManagerFactory.close method to destroy the entity manager factory prior to shutdown (if it has not been previously closed by the application). > 7.8.2 Container Managed Persistence Contexts > The container is responsible for managing the lifecycle of container-managed persistence contexts, for injecting EntityManager references into web components and session bean and message-driven bean components, and for making EntityManager references available to direct lookups in JNDI. When operating with a third-party persistence provider, the container uses the contracts defined in section 7.9 to create and destroy container-managed persistence contexts. It is undefined whether a new entity manager instance is created for every persistence context, or whether entity manager instances are sometimes reused. Exactly how the container maintains the association between persistence context and JTA transaction is not defined. If a persistence context is already associated with a JTA transaction, the container uses that persistence context for subsequent invocations within the scope of that transaction, according to the semantics for persistence context propagation defined in section 7.6.4. > 7.9 Runtime Contracts between the Container and Persistence Provider > This section describes contracts between the container and the persistence provider for the pluggability of third-party persistence providers. Containers are required to support these pluggability contracts. [87] > 7.9.1 Container Responsibilities > For the management of a transaction-scoped persistence context, if there is no EntityManager already associated with the JTA transaction: > * The container creates a new entity manager by calling EntityManagerFactory.createEntityManager when the first invocation of an entity manager with PersistenceContextType.TRANSACTION occurs within the scope of a business method executing in the JTA transaction. > * After the JTA transaction has completed (either by transaction commit or rollback), the container closes the entity manager by calling EntityManager.close. [88] Note that the JTA transaction may rollback in a background thread (e.g., as a result of transaction timeout), in which case the container should arrange for the entity manager to be closed but the EntityManager.close method should not be concurrently invoked while the application is in an EntityManager invocation. > The container must throw the TransactionRequiredException if a transaction-scoped persistence context is used and the EntityManager persist, remove, merge, or refresh method is invoked when no transaction is active. > For stateful session beans with extended persistence contexts: > * The container creates an entity manager by calling EntityManagerFactory.createEntityManager when a stateful session bean is created that declares a dependency on an entity manager with PersistenceContextType.EXTENDED. (See section 7.6.3). > * The container closes the entity manager by calling EntityManager.close after the stateful session bean and all other stateful session beans that have inherited the same persistence context as the entity manager have been removed. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses container managed transaction demarcation, and the entity manager is not already associated with the current JTA transaction, the container associates the entity manager with the current JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. If there is a different persistence context already associated with the JTA transaction, the container throws the EJBException. > * When a business method of the stateful session bean is invoked, if the stateful session bean uses bean managed transaction demarcation and a UserTransaction is begun within the method, the container associates the persistence context with the JTA transaction and, if the persistence context is of type SynchronizationType.SYNCHRONIZED, the container calls EntityManager.joinTransaction. > The container must throw the IllegalStateException if the application calls EntityManager.close on a container-managed entity manager. > [87] It is not required that these contracts be used when a third-party persistence provider is not used: the container might use these same APIs or its might use its own internal APIs. > [88] The container may choose to pool EntityManagers: it instead of creating and closing in each case, it may acquire one from its pool and call clear() on it. > {quote} > One challenge with introducing an entity manager (per EntityManagerFactory) cache, is knowing when to close EntityManagers after certain errors have occurred on the EntityManager. To deal with this robustness issue, we will discard entity managers that are marked close when retrieving them from the cache. > We currently keep strong references to the (cleared) EntityManager's from the cache. If this causes OOM errors, we could consider using SOFT references so that the EntityManager's could be GCd in low memory conditions. > Code changes will likely be: > * In [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], we can try to retrieve an entity manager from the cache (cache reference can be passed into the TransactionScopedEntityManager proxy constructor), if cache is empty, then create a new entity manager to return. > * In https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav..., if caching is enabled, we should call EntityManager.clear(), instead of EntityManager.close(), however, if an exception is thrown (on call to em.clear()), the entity manager shouldn't be put in the cache, instead we can try to close it and log/ignore any further exception thrown by the call to em.close(). > * If an entity manager is in a bad state, we shouldn't place it back in the cache. This may really be the same as the previous bullet but I wanted to mention it as a separate bullet, since we may need to add more error checking for the persistence throwing exceptions in [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...] or/and other places. Not Implemented yet. > * In [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], if caching is enabled, we should call EntityManager.clear() instead of EntityManager.close(), however, if an exception is thrown (on call to em.clear()), the entity manager shouldn't be put in the cache, instead we can try to close it and log/ignore any any further exception thrown by the call to em.close(). > * Lastly, we should update [https://github.com/wildfly/wildfly/blob/master/jpa/subsystem/src/main/jav...], to deal with releasing the entity manager cache before calling entityManagerFactory.close(). Since, [https://docs.oracle.com/javaee/7/api/javax/persistence/EntityManagerFacto...] says that the entity managers will be closed automatically, we can just clear the cache of EntityManagers, instead of actually calling EntityManager.close() on each one in the cache. > * Also ensure that SynchronizationType is respected, so we don't mix SynchronizationType.UNSYNCHRONIZED + SynchronizationType.SYNCHRONIZED types. We will only cache SynchronizationType.SYNCHRONIZED. > Persistence unit hint "wildfly.jpa.emcache", may be: > * true, per EntityManagerFactory/persistence unit) cache that is shared between multiple threads. > * false (default), no caching is performed. > To ensure that we always put the cached EM back in cache, cache use is only done within JTA transactions, since we have control of the release (closing) of the EntityManager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1704) Release WildFly Elytron 1.1.12.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1704?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1704: ---------------------------------- Summary: Release WildFly Elytron 1.1.12.Final (was: Release WildFly Elytron 1.1.12) > Release WildFly Elytron 1.1.12.Final > ------------------------------------ > > Key: ELY-1704 > URL: https://issues.jboss.org/browse/ELY-1704 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.1.12.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2313) Promote GMS message "[...] creating cluster as first member" to INFO level

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2313?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2313: --------------------------- Fix Version/s: 4.0.16 > Promote GMS message "[...] creating cluster as first member" to INFO level > -------------------------------------------------------------------------- > > Key: JGRP-2313 > URL: https://issues.jboss.org/browse/JGRP-2313 > Project: JGroups > Issue Type: Enhancement > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 4.0.16 > > > This message is quite informative and should be rarely logged (only when booting the entire cluster) but can be helful situations when discovery does not work or does not work fast enough. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3224: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > h2. Manaul acceptance test > Autolayout is applied: > - for asset linked above > - for [^DMCommunity Challenge - March 2017.dmn] > - For 1.2 based assets -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3224: -------------------------------------- Assignee: Michael Anstis (was: Daniel José dos Santos) > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > h2. Manaul acceptance test > Autolayout is applied: > - for asset linked above > - for [^DMCommunity Challenge - March 2017.dmn] > - For 1.2 based assets -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3224: ----------------------------------- Sprint: 2018 Week 42-44 > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > h2. Manaul acceptance test > Autolayout is applied: > - for asset linked above > - for [^DMCommunity Challenge - March 2017.dmn] > - For 1.2 based assets -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1704) Release WildFly Elytron 1.1.12

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1704: ------------------------------------- Summary: Release WildFly Elytron 1.1.12 Key: ELY-1704 URL: https://issues.jboss.org/browse/ELY-1704 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.12.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2313) Promote GMS message "[...] creating cluster as first member" to INFO level

by Radoslav Husar (Jira)

Radoslav Husar created JGRP-2313: ------------------------------------ Summary: Promote GMS message "[...] creating cluster as first member" to INFO level Key: JGRP-2313 URL: https://issues.jboss.org/browse/JGRP-2313 Project: JGroups Issue Type: Enhancement Reporter: Radoslav Husar Assignee: Bela Ban This message is quite informative and should be rarely logged (only when booting the entire cluster) but can be helful situations when discovery does not work or does not work fast enough. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2313) Promote GMS message "[...] creating cluster as first member" to INFO level

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/JGRP-2313?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned JGRP-2313: ------------------------------------ Assignee: Radoslav Husar (was: Bela Ban) > Promote GMS message "[...] creating cluster as first member" to INFO level > -------------------------------------------------------------------------- > > Key: JGRP-2313 > URL: https://issues.jboss.org/browse/JGRP-2313 > Project: JGroups > Issue Type: Enhancement > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > This message is quite informative and should be rarely logged (only when booting the entire cluster) but can be helful situations when discovery does not work or does not work fast enough. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3215) Copying an empty folder in MemoryFileSystem fails with NPE

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3215?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-3215: ----------------------------------- Assignee: Mario Fusco (was: Tibor Zimányi) > Copying an empty folder in MemoryFileSystem fails with NPE > ---------------------------------------------------------- > > Key: DROOLS-3215 > URL: https://issues.jboss.org/browse/DROOLS-3215 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.13.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Priority: Major > Fix For: 7.14.0.Final > > > When this test [1] is put into MemoryFileSystemTest and run, it ends with NullPointerException. The thing that triggers it is creating the folder with getFolder() method. > [1] https://gist.github.com/baldimir/d6bac6de418eba1252e2d20cebaaad45 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 November 2018