September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-11010: ------------------------------------- Below is TRACE output for org.jipijapa enabled while deploying a few different apps: {quote} 2018-09-25 09:42:31,467 TRACE [org.jipijapa] (ServerService Thread Pool -- 73) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:42:31,467 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:42:31,655 TRACE [org.jipijapa] (ServerService Thread Pool -- 74) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:42:31,657 TRACE [org.jipijapa] (ServerService Thread Pool -- 75) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:42:41,576 TRACE [org.jipijapa] (ServerService Thread Pool -- 73) ServiceContributorImpl#contribute application is using Ehcache via regionFactory=net.sf.ehcache.hibernate.EhCacheRegionFactory 2018-09-25 09:43:15,122 TRACE [org.jipijapa] (ServerService Thread Pool -- 75) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:43:15,153 TRACE [org.jipijapa] (ServerService Thread Pool -- 75) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory using org.infinispan.hibernate.cache.v53.InfinispanRegionFactory for 2lc, useSecondLevelCache=true, jpaSharedCodeModeValue=ENABLE_SELECTIVE, regionFactory=org.infinispan.hibernate.cache.v53.InfinispanRegionFactory 2018-09-25 09:43:19,842 TRACE [org.jipijapa] (ServerService Thread Pool -- 74) ServiceContributorImpl#contribute application is using Ehcache via regionFactory=net.sf.ehcache.hibernate.EhCacheRegionFactory 2018-09-25 09:43:32,690 TRACE [org.jipijapa] (MSC service thread 1-2) second level cache enabled for 2lc.jar#TEST_PU 2018-09-25 09:43:32,711 TRACE [org.jipijapa] (MSC service thread 1-2) second level cache disabled for 2lc.jar#second_PU, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE 2018-09-25 09:43:46,167 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:43:46,169 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory using org.infinispan.hibernate.cache.v53.InfinispanRegionFactory for 2lc, useSecondLevelCache=true, jpaSharedCodeModeValue=NONE, regionFactory=null 2018-09-25 09:45:03,479 TRACE [org.jipijapa] (MSC service thread 1-5) second level cache disabled for MultiplePuTestCase.jar#pu2, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = UNSPECIFIED 2018-09-25 09:45:03,480 TRACE [org.jipijapa] (MSC service thread 1-5) second level cache disabled for MultiplePuTestCase.jar#pu1, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = UNSPECIFIED 2018-09-25 09:45:03,487 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:45:03,487 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:45:03,525 TRACE [org.jipijapa] (ServerService Thread Pool -- 78) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:45:03,525 TRACE [org.jipijapa] (ServerService Thread Pool -- 78) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:45:04,022 TRACE [org.jipijapa] (MSC service thread 1-6) second level cache disabled for MultiplePuTestCase.jar#pu2, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE 2018-09-25 09:45:04,024 TRACE [org.jipijapa] (MSC service thread 1-6) second level cache disabled for MultiplePuTestCase.jar#pu1, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE 2018-09-25 09:45:14,514 TRACE [org.jipijapa] (ServerService Thread Pool -- 72) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory not using a 2lc, useSecondLevelCache=null, jpaSharedCodeModeValue=NONE, regionFactory=null 2018-09-25 09:45:16,574 TRACE [org.jipijapa] (ServerService Thread Pool -- 78) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory not using a 2lc, useSecondLevelCache=null, jpaSharedCodeModeValue=NONE, regionFactory=null 2018-09-25 09:47:40,713 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache disabled for JpaStatisticsTestCase.jar#mypc_no_2lc, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE 2018-09-25 09:47:40,714 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache enabled for JpaStatisticsTestCase.jar#mypc2 2018-09-25 09:47:40,714 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache enabled for JpaStatisticsTestCase.jar#mypc 2018-09-25 09:47:40,728 TRACE [org.jipijapa] (ServerService Thread Pool -- 80) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:47:40,729 TRACE [org.jipijapa] (ServerService Thread Pool -- 80) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:47:40,729 TRACE [org.jipijapa] (ServerService Thread Pool -- 80) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory not using a 2lc, useSecondLevelCache=false, jpaSharedCodeModeValue=NONE, regionFactory=null 2018-09-25 09:47:40,735 TRACE [org.jipijapa] (ServerService Thread Pool -- 84) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:47:40,735 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:47:40,736 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:47:40,736 TRACE [org.jipijapa] (ServerService Thread Pool -- 84) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:47:40,736 TRACE [org.jipijapa] (ServerService Thread Pool -- 84) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory using org.infinispan.hibernate.cache.v53.InfinispanRegionFactory for 2lc, useSecondLevelCache=true, jpaSharedCodeModeValue=ENABLE_SELECTIVE, regionFactory=org.infinispan.hibernate.cache.v53.InfinispanRegionFactory 2018-09-25 09:47:40,736 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory using org.infinispan.hibernate.cache.v53.InfinispanRegionFactory for 2lc, useSecondLevelCache=true, jpaSharedCodeModeValue=ENABLE_SELECTIVE, regionFactory=org.infinispan.hibernate.cache.v53.InfinispanRegionFactory 2018-09-25 09:47:40,785 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache disabled for JpaStatisticsTestCase.jar#mypc_no_2lc, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE 2018-09-25 09:47:40,786 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache enabled for JpaStatisticsTestCase.jar#mypc2 2018-09-25 09:47:40,786 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache enabled for JpaStatisticsTestCase.jar#mypc 2018-09-25 09:49:25,370 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache disabled for jpa_emfactory.jar#mypc, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = UNSPECIFIED 2018-09-25 09:49:25,372 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) ServiceContributorImpl#contribute application will use WildFlyCustomJtaPlatform 2018-09-25 09:49:25,372 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) ServiceContributorImpl#contribute adding ORM initiator for 2lc region factory 2018-09-25 09:49:25,373 TRACE [org.jipijapa] (ServerService Thread Pool -- 83) WildFlyCustomRegionFactoryInitiator#resolveRegionFactory not using a 2lc, useSecondLevelCache=null, jpaSharedCodeModeValue=NONE, regionFactory=null 2018-09-25 09:49:25,391 TRACE [org.jipijapa] (MSC service thread 1-1) second level cache disabled for jpa_emfactory.jar#mypc, pu javax.persistence.sharedCache.mode property = null, pu.getSharedCacheMode = NONE {quote} > Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11010 > URL: https://issues.jboss.org/browse/WFLY-11010 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 15.0.0.Alpha1 > > > Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration. > Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache. > Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform". This should help applications that have configured to use JTA transaction factory or transaction platform classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3034) Add possibility to import a cucumber feature file

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3034?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3034: --------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 39-41) > Add possibility to import a cucumber feature file > ------------------------------------------------- > > Key: DROOLS-3034 > URL: https://issues.jboss.org/browse/DROOLS-3034 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > > As user I would like to have the possibility to import an existing Cucumber feature file to create a test scenario -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-10339?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-10339: ------------------------------------- [~ehugonnet] {quote}Isn't the use of capabilities be sufficient to fix this without creating new resources in the model ?{quote} As I mentioned above, we already use capability references for the jgroups vs multicast attributes. The issue is that the requirements for the resource are determined by whether or not the jgroups-cluster attribute is defined. I had to make a similar change for the singleton subsystem, where the requirements for the resource were determined by whether or not the "cache" attribute was defined (remember the whole DefaultableCapabilityReference stuff?) > Broadcast/discovery-group resources have ambiguous requirement specs > -------------------------------------------------------------------- > > Key: WFLY-10339 > URL: https://issues.jboss.org/browse/WFLY-10339 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. > I suggest splitting these resources into 2: > {code}/subsystem=messaging-activemq/server=*/jgroups-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/jgroups-discovery-group=*{code} > which requires clustering capabilities > and > {code}/subsystem=messaging-activemq/server=*/socket-broadcast-group=*{code} > {code}/subsystem=messaging-activemq/server=*/socket-discovery-group=*{code} > which requires a socket-binding capability. > This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2960) User should be able to use Scenario Simulation asset with the distribution war

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2960?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2960: --------------------------------- Story Points: 1 (was: 3) > User should be able to use Scenario Simulation asset with the distribution war > ------------------------------------------------------------------------------ > > Key: DROOLS-2960 > URL: https://issues.jboss.org/browse/DROOLS-2960 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Toni Rikkola > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2676) Input actual data into data fields

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2676?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2676: --------------------------------- Story Points: 2 (was: 5) > Input actual data into data fields > ---------------------------------- > > Key: DROOLS-2676 > URL: https://issues.jboss.org/browse/DROOLS-2676 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to input actual data into data fields so that I can run a single scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2959) Create initial content for Scenario Simulation documentation.

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2959?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2959: --------------------------------- Story Points: 1 (was: 3) > Create initial content for Scenario Simulation documentation. > ------------------------------------------------------------- > > Key: DROOLS-2959 > URL: https://issues.jboss.org/browse/DROOLS-2959 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Klara Kufova > > As a user I would like to know that this new tool exists and how to use it :-) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2788: -------------------------------- Story Points: 3 (was: 5) > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-2788 > URL: https://issues.jboss.org/browse/DROOLS-2788 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png > > > As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2678) The ability to upload an external spreadsheet

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2678?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2678: --------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 39-41) > The ability to upload an external spreadsheet > --------------------------------------------- > > Key: DROOLS-2678 > URL: https://issues.jboss.org/browse/DROOLS-2678 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business user I want the ability to upload an external spreadsheet so that I can speed up scenario data input. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2869) Use a dock component in the right panel to match the UX proposal

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2869?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2869: --------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 39-41) > Use a dock component in the right panel to match the UX proposal > ---------------------------------------------------------------- > > Key: DROOLS-2869 > URL: https://issues.jboss.org/browse/DROOLS-2869 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > > Update right panel interation to match UX proposal -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2869) Use a dock component in the right panel to match the UX proposal

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2869?page=com.atlassian.jira.plugi... ] Klara Kufova reassigned DROOLS-2869: ------------------------------------ Assignee: Toni Rikkola (was: Gabriele Cardosi) > Use a dock component in the right panel to match the UX proposal > ---------------------------------------------------------------- > > Key: DROOLS-2869 > URL: https://issues.jboss.org/browse/DROOLS-2869 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > > Update right panel interation to match UX proposal -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 September 2018