March 2019 - 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 commented on WFLY-11233: ------------------------------------- For future reference [https://www.ibm.com/support/knowledgecenter/SS7K4U_8.5.5/com.ibm.webspher...] describes Websphere entityManagerPoolCapacity setting. > 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 > 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. To ensure that we always put the cached EM back in cache, EntityManagerCache use is only done within JTA transactions, since we have control of the release (closing) of the EntityManager and only with SynchronizationType.SYNCHRONIZED (never with SynchronizationType.UNSYNCHRONIZED) persistence contexts. > For this jira, the EntityManagerCache keeps strong references to the (cleared) EntityManager's from the cache. If this causes users OOM errors, we could consider using SOFT references so that the EntityManager's could be GCd in low memory conditions. We also offer users a choice between an unbounded cache (size=0) and a bounded cache. Users that have problems with OOM errors, should switch to a bounded cache. > 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. > Persistence unit hint "wildfly.jpa.emcache.size", may be: > * 0 (default), the cache (if enabled) is unbounded. > * N, where N is the max number of EntityManager instances that can be placed in the EntityManagerCache, in between application use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11840) Periodic recovery does not recover XAResource after jvm crash when agroal subsystem is used

by Kabir Khan (Jira)

Kabir Khan created WFLY-11840: --------------------------------- Summary: Periodic recovery does not recover XAResource after jvm crash when agroal subsystem is used Key: WFLY-11840 URL: https://issues.jboss.org/browse/WFLY-11840 Project: WildFly Issue Type: Bug Components: Agroal, Transactions Reporter: Ivan Straka Assignee: Luis Barreiro Fix For: 17.0.0.Beta1 Scenario: Halts server at commit phase ... # enlist TestXA resource # enlist XA resource # prepare TestXA resource # prepare XA resource # commit Test XA resource # JVM crash # recovery started # commit XA resource Periodic recovery does not recover xa resource. It looks like agroal subsystem does not register xa resource to xa recovery module. Test outcome: {code:java} Running org.jboss.as.test.jbossts.crashrec.test.JPACrashRecoveryTestCase Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.002 sec <<< FAILURE! - in org.jboss.as.test.jbossts.crashrec.test.JPACrashRecoveryTestCase commitHaltSecond(org.jboss.as.test.jbossts.crashrec.test.JPACrashRecoveryTestCase) Time elapsed: 102.976 sec <<< FAILURE! java.lang.AssertionError: Incorrect data in database after crash recovery. expected:<2> but was:<1> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.jboss.as.test.jbossts.crashrec.test.JPABaseCrashRecoveryTestCase.checkAfterTestExecution(JPABaseCrashRecoveryTestCase.java:150) at org.jboss.as.test.jbossts.crashrec.test.TestBaseCrashRecovery.commitHaltTest(TestBaseCrashRecovery.java:485) at org.jboss.as.test.jbossts.crashrec.test.TestBaseCrashRecovery.commitHaltSecond(TestBaseCrashRecovery.java:418) at org.jboss.as.test.jbossts.crashrec.test.JPACrashRecoveryTestCase.commitHaltSecond(JPACrashRecoveryTestCase.java:76) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3097) Add support to import/export data from Scenario

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3097?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3097: --------------------------------- Story Points: 8 > Add support to import/export data from Scenario > ----------------------------------------------- > > Key: DROOLS-3097 > URL: https://issues.jboss.org/browse/DROOLS-3097 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > As user I want to be able to import and export data from a scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3608: --------------------------------- Story Points: 8 (was: 9) > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3592) Investigate: Undo/Redo regression on right panel

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3592?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3592: ------------------------------------- Issue Type: Task (was: Bug) > Investigate: Undo/Redo regression on right panel > ------------------------------------------------ > > Key: DROOLS-3592 > URL: https://issues.jboss.org/browse/DROOLS-3592 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > After naming/renaming of header, undo/redo does not restore correctly the right panel status. > Start this ticket after merging of DROOLS-3242, DROOLS-3357, DROOLS-3466, DROOLS-3485, DROOLS-3568 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3592) Investigate: Undo/Redo regression on right panel

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3592?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3592: --------------------------------- Sprint: 2019 Week 08-10 (was: 2019 Week 08-10, 2019 Week 11-13) > Investigate: Undo/Redo regression on right panel > ------------------------------------------------ > > Key: DROOLS-3592 > URL: https://issues.jboss.org/browse/DROOLS-3592 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > After naming/renaming of header, undo/redo does not restore correctly the right panel status. > Start this ticket after merging of DROOLS-3242, DROOLS-3357, DROOLS-3466, DROOLS-3485, DROOLS-3568 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3163) Add toolbar controls for editing the table.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3163?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3163 at 3/12/19 10:34 AM: --------------------------------------------------------------- [~kkufova][~ibek] There is a sister jira on the DMN side: https://issues.jboss.org/browse/BAPL-991. Depending on what happens there, it might still be relevant. was (Author: uxdlc): [~kkufova][~ibek] There is a sister jira on the DMN side: https://issues.jboss.org/browse/DROOLS-3163. Depending on what happens there, it might still be relevant. > Add toolbar controls for editing the table. > -------------------------------------------- > > Key: DROOLS-3163 > URL: https://issues.jboss.org/browse/DROOLS-3163 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Ivo Bek > Priority: Major > Labels: UX-CSS > Attachments: Screen Shot 2018-10-19 at 2.32.04 PM.png > > > As a novice user of this feature I would like a simple control to edit the table (insert row etc), so that I can quickly learn how to use this tool. > Note: To align the design with both the wireframes and with similar editors (DMN) the table should offer a dropdown above the table to allow simple table structure edits. As illustrated in the wireframe click-thru: https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476078 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3741) Create HTML/CSS for Test scenario coverage report

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3741?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3741: --------------------------------- Story Points: 3 > Create HTML/CSS for Test scenario coverage report > ------------------------------------------------- > > Key: DROOLS-3741 > URL: https://issues.jboss.org/browse/DROOLS-3741 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Sarah Rambacher > Priority: Major > Labels: ScenarioSimulation > > Create HTML/CSS for this new dock component > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3163) Add toolbar controls for editing the table.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3163?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3163: ------------------------------------- [~kkufova][~ibek] There is a sister jira on the DMN side: https://issues.jboss.org/browse/DROOLS-3163. Depending on what happens there, it might still be relevant. > Add toolbar controls for editing the table. > -------------------------------------------- > > Key: DROOLS-3163 > URL: https://issues.jboss.org/browse/DROOLS-3163 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Ivo Bek > Priority: Major > Labels: UX-CSS > Attachments: Screen Shot 2018-10-19 at 2.32.04 PM.png > > > As a novice user of this feature I would like a simple control to edit the table (insert row etc), so that I can quickly learn how to use this tool. > Note: To align the design with both the wireframes and with similar editors (DMN) the table should offer a dropdown above the table to allow simple table structure edits. As illustrated in the wireframe click-thru: https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476078 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3730) Add support to DMN constraints on inputs (report input validation errors)

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3730?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3730: --------------------------------- Story Points: 8 > Add support to DMN constraints on inputs (report input validation errors) > ------------------------------------------------------------------------- > > Key: DROOLS-3730 > URL: https://issues.jboss.org/browse/DROOLS-3730 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > See this example https://github.com/kiegroup/drools/compare/master...tarilabs:tarilabs-201... > and try with a value out of the domain ranga [0..100]. > when a Decision or any evaluation which depends on such InputData is triggered, an error message like the following is reported > ```Error while evaluating node 'my decision' for dependency 'my input': the dependency value '999' is not allowed by the declared type (DMNType{ http://www.trisotech.com/definitions/_7ab67159-21c7-4985-91fc-f0d0174898db : tNumber0100 })``` -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 March 2019