October 2018 - jboss-jira - Jboss List Archives

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

by Scott Marlow (Jira)

Scott Marlow created WFLY-11233: ----------------------------------- Summary: allow EntityManager caching in the JPA container Key: WFLY-11233 URL: https://issues.jboss.org/browse/WFLY-11233 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate Reporter: Scott Marlow 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: {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). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11232) Upgrade jboss-ejb-client from 4.0.11 to 4.0.12

by James Perkins (Jira)

James Perkins created WFLY-11232: ------------------------------------ Summary: Upgrade jboss-ejb-client from 4.0.11 to 4.0.12 Key: WFLY-11232 URL: https://issues.jboss.org/browse/WFLY-11232 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: James Perkins Assignee: James Perkins There is a single fix in the upgrade https://github.com/wildfly/jboss-ejb-client/compare/4.0.11.Final...4.0.12... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4177) LegacyKernelServiceInitializerImpl.reverseCheckConfig should default to AdditionalInitialization.MANAGEMENT

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4177?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-4177: ---------------------------------------- Assignee: Brian Stansberry (was: Jeff Mesnil) > LegacyKernelServiceInitializerImpl.reverseCheckConfig should default to AdditionalInitialization.MANAGEMENT > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4177 > URL: https://issues.jboss.org/browse/WFCORE-4177 > Project: WildFly Core > Issue Type: Enhancement > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > LegacyKernelServiceInitializerImpl.reverseCheckConfig is only used in bootCurrentVersionWithLegacyBootOperations and in that test I don't see any point in using non-management services. But to disable those, the user has to LegacyKernelServicesInitializer.configureReverseControllerCheck(AdditionalInitialization.MANAGEMENT, null). Which is obscure and seems unnecessary. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4177) LegacyKernelServiceInitializerImpl.reverseCheckConfig should default to AdditionalInitialization.MANAGEMENT

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4177: ---------------------------------------- Summary: LegacyKernelServiceInitializerImpl.reverseCheckConfig should default to AdditionalInitialization.MANAGEMENT Key: WFCORE-4177 URL: https://issues.jboss.org/browse/WFCORE-4177 Project: WildFly Core Issue Type: Enhancement Components: Management, Test Suite Reporter: Brian Stansberry Assignee: Jeff Mesnil LegacyKernelServiceInitializerImpl.reverseCheckConfig is only used in bootCurrentVersionWithLegacyBootOperations and in that test I don't see any point in using non-management services. But to disable those, the user has to LegacyKernelServicesInitializer.configureReverseControllerCheck(AdditionalInitialization.MANAGEMENT, null). Which is obscure and seems unnecessary. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2307) JGroups crashes when slf4j is used (Slf4jLogImpl)

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2307: --------------------------- Fix Version/s: 4.0.16 > JGroups crashes when slf4j is used (Slf4jLogImpl) > ------------------------------------------------- > > Key: JGRP-2307 > URL: https://issues.jboss.org/browse/JGRP-2307 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6, 4.0.15 > Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected > - Only happens in docker (our image is based on "java:8") > Reporter: Daan Wendelen > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.16 > > Attachments: jgroups-bug.zip > > > When running our application, it crashes with the following stacktrace. > {code} > Exception in thread "main" java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) > at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) > at org.springframework.boot.loader.Launcher.launch(Launcher.java:50) > at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51) > Caused by: java.lang.ExceptionInInitializerError > at Bug.main(Bug.java:5) > ... 8 more > Caused by: java.lang.NullPointerException > at java.util.Locale.<init>(Locale.java:648) > at java.util.Locale.<init>(Locale.java:677) > at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20) > ... 9 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2307) JGroups crashes when slf4j is used (Slf4jLogImpl)

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2307?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2307: --------------------------- Summary: JGroups crashes when slf4j is used (Slf4jLogImpl) (was: Jgroup crashes when slf4j is used (Slf4jLogImpl)) > JGroups crashes when slf4j is used (Slf4jLogImpl) > ------------------------------------------------- > > Key: JGRP-2307 > URL: https://issues.jboss.org/browse/JGRP-2307 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6, 4.0.15 > Environment: - I only tested 4.0.6 and 4.0.15 but I suspect all 4.0.x version are affected > - Only happens in docker (our image is based on "java:8") > Reporter: Daan Wendelen > Assignee: Bela Ban > Priority: Major > Attachments: jgroups-bug.zip > > > When running our application, it crashes with the following stacktrace. > {code} > Exception in thread "main" java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) > at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) > at org.springframework.boot.loader.Launcher.launch(Launcher.java:50) > at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51) > Caused by: java.lang.ExceptionInInitializerError > at Bug.main(Bug.java:5) > ... 8 more > Caused by: java.lang.NullPointerException > at java.util.Locale.<init>(Locale.java:648) > at java.util.Locale.<init>(Locale.java:677) > at org.jgroups.logging.Slf4jLogImpl.<clinit>(Slf4jLogImpl.java:20) > ... 9 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-464) Bookinfo installation fails on B18/12

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-464?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-464: ------------------------------------- First problem from first comment is only visible on ansible jenkins slave with ansible 2.7. The k8s ansible modul should use server defined in oc config current-context but it's not doing it for some reason with this ansible version. Result is that it's using b22 as default. > Bookinfo installation fails on B18/12 > ------------------------------------- > > Key: SWSQE-464 > URL: https://issues.jboss.org/browse/SWSQE-464 > Project: Kiali QE > Issue Type: Bug > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > Attachments: install_bookinfo.log, istio_upstream.log > > > Failing with different param runs: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) Add support for map and list

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3098: --------------------------------------- [~uxdlc][~ibek] Yes it is related to the right panel but not only. At the moment there is no way to use interact with lists or maps available into DO so if user has one or more list/map, cannot be selected from the right panel nor defined the values into the table. How can the user work with list/map? How can the user access a list/map (for a map he needs to specify the key at least I think)? > Add support for map and list > ---------------------------- > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > 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 use Data Objects that contain Lists and Maps -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-464) Bookinfo installation fails on B18/12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-464?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo edited comment on SWSQE-464 at 10/23/18 10:53 AM: -------------------------------------------------------------------------- I executed locally with oc connected to b16 and it worked with istio-1.1.0 snapshot and ansible 2.7 Logs Attached [^install_bookinfo.log] [^istio_upstream.log] (ansible --version ansible 2.7.0 config file = None configured module search path = ['/Users/gbaufake/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/local/lib/python3.7/site-packages/ansible executable location = /usr/local/bin/ansible python version = 3.7.0 (default, Oct 2 2018, 09:18:58) [Clang 10.0.0 (clang-1000.11.45.2)]) (istioctl version version.BuildInfo{Version:"1.1.0.snapshot.1", GitRevision:"45692c579c6d755194421540149a99ac4cb59528", User:"root", Host:"ac7ff4b30ee4", GolangVersion:"go1.10.1", DockerHub:"gcr.io/istio-release", BuildStatus:"Clean"}) was (Author: gbaufake): I executed locally with oc connected to b16 and it worked with istio-1.1.0 snapshot and ansible 2.7 Logs Attached [^install_bookinfo.log] [^istio_upstream.log] > Bookinfo installation fails on B18/12 > ------------------------------------- > > Key: SWSQE-464 > URL: https://issues.jboss.org/browse/SWSQE-464 > Project: Kiali QE > Issue Type: Bug > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > Attachments: install_bookinfo.log, istio_upstream.log > > > Failing with different param runs: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3126) Scenario Design Requirements (dev/ux)

by Ivo Bek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3126?page=com.atlassian.jira.plugi... ] Ivo Bek updated DROOLS-3126: ---------------------------- Summary: Scenario Design Requirements (dev/ux) (was: Scenario enhancements (dev/ux)) > Scenario Design Requirements (dev/ux) > ------------------------------------- > > Key: DROOLS-3126 > URL: https://issues.jboss.org/browse/DROOLS-3126 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Daniele Zonca > Assignee: Liz Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UX-CSS, UXTeam > > User story: As a user of this feature I want a consistent user experience so I can move seamlessly between editors and product features. > *Table/grid visual styling*: > * align with DMN and GDT. Refer to related epic: https://issues.jboss.org/browse/DROOLS-2942 > * resolve table width issue. > * provide Table edit dropdown control. > *Docks/panels*: track enhancements with known issues in workbench, see linked jiras. > - For scenario specific bugs see: See https://issues.jboss.org/browse/DROOLS-3154 > - use docks component, (remove "hide right panel" button from toolbar): https://issues.jboss.org/browse/DROOLS-2869 > *Contextual menus & pop-overs* - verify cross product-feature alignment where applicable. > Working documented at: https://docs.google.com/document/d/1lHQ1mvmzQcgWbxwkBobIXb9mV6uM3RLbEll8-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018