June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1999) Upgrade JBoss Threads to 2.3.5.Final

by Farah Juma (Jira)

Farah Juma created ELY-1999: ------------------------------- Summary: Upgrade JBoss Threads to 2.3.5.Final Key: ELY-1999 URL: https://issues.redhat.com/browse/ELY-1999 Project: WildFly Elytron Issue Type: Component Upgrade Components: Build Reporter: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13617) Hibernate DataSourceBasedMultiTenantConnectionProviderImpl does not work for Multitenancy

by Rafael Sampaio (Jira)

[ https://issues.redhat.com/browse/WFLY-13617?page=com.atlassian.jira.plugi... ] Rafael Sampaio updated WFLY-13617: ---------------------------------- Priority: Minor (was: Major) > Hibernate DataSourceBasedMultiTenantConnectionProviderImpl does not work for Multitenancy > ----------------------------------------------------------------------------------------- > > Key: WFLY-13617 > URL: https://issues.redhat.com/browse/WFLY-13617 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 19.1.0.Final, 20.0.0.Final > Reporter: Rafael Sampaio > Assignee: Scott Marlow > Priority: Minor > > Hello All, > I was using o the DataSourceBasedMultiTenantConnectionProviderImpl contained in Hibernate lib to perform DATABASE MultitenancyType up to Wildfly 18. > Upgrading to version 19 (tested on 20 too), upon initialization of my application I get the error: > > {noformat} > 14:07:52,655 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service jboss.persistenceunit."web-5.0.0#appPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."web-5.0.0#appPU": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]14:07:52,655 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service jboss.persistenceunit."web-5.0.0#appPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."web-5.0.0#appPU": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:658) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485)Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152) at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179) at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246) at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170) ... 9 more > Caused by: org.hibernate.HibernateException: Improper set up of DataSourceBasedMultiTenantConnectionProviderImpl at org.hibernate.engine.jdbc.connections.spi.DataSourceBasedMultiTenantConnectionProviderImpl.injectServices(DataSourceBasedMultiTenantConnectionProviderImpl.java:80) at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.buildJdbcConnectionAccess(JdbcEnvironmentInitiator.java:149) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:66) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35) at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94) at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263) ... 21 more{noformat} > The error happens inside this implementation: > > > {noformat} > public void injectServices(ServiceRegistryImplementor serviceRegistry) { > final Object dataSourceConfigValue = serviceRegistry.getService( ConfigurationService.class ) > .getSettings() > .get( AvailableSettings.DATASOURCE ); > if ( dataSourceConfigValue == null || ! String.class.isInstance( dataSourceConfigValue ) ) { > throw new HibernateException( "Improper set up of DataSourceBasedMultiTenantConnectionProviderImpl" ); > } > ...{noformat} > The changed behavior is that the the parameter is no longer a String, but a WildFlyDataSource. > > I'm opening this case just to check if this is the expected behavior, and I should really override the necessary part of the code in order to circumvent the error or was this some sort of regression? > Kindly, > Rafael Sampaio > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13617) Hibernate DataSourceBasedMultiTenantConnectionProviderImpl does not work for Multitenancy

by Rafael Sampaio (Jira)

Rafael Sampaio created WFLY-13617: ------------------------------------- Summary: Hibernate DataSourceBasedMultiTenantConnectionProviderImpl does not work for Multitenancy Key: WFLY-13617 URL: https://issues.redhat.com/browse/WFLY-13617 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 20.0.0.Final, 19.1.0.Final Reporter: Rafael Sampaio Assignee: Scott Marlow Hello All, I was using o the DataSourceBasedMultiTenantConnectionProviderImpl contained in Hibernate lib to perform DATABASE MultitenancyType up to Wildfly 18. Upgrading to version 19 (tested on 20 too), upon initialization of my application I get the error: {noformat} 14:07:52,655 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service jboss.persistenceunit."web-5.0.0#appPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."web-5.0.0#appPU": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]14:07:52,655 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service jboss.persistenceunit."web-5.0.0#appPU": org.jboss.msc.service.StartException in service jboss.persistenceunit."web-5.0.0#appPU": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:658) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485)Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment] at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152) at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179) at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215) at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246) at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170) ... 9 more Caused by: org.hibernate.HibernateException: Improper set up of DataSourceBasedMultiTenantConnectionProviderImpl at org.hibernate.engine.jdbc.connections.spi.DataSourceBasedMultiTenantConnectionProviderImpl.injectServices(DataSourceBasedMultiTenantConnectionProviderImpl.java:80) at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.buildJdbcConnectionAccess(JdbcEnvironmentInitiator.java:149) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:66) at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35) at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94) at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263) ... 21 more{noformat} The error happens inside this implementation: {noformat} public void injectServices(ServiceRegistryImplementor serviceRegistry) { final Object dataSourceConfigValue = serviceRegistry.getService( ConfigurationService.class ) .getSettings() .get( AvailableSettings.DATASOURCE ); if ( dataSourceConfigValue == null || ! String.class.isInstance( dataSourceConfigValue ) ) { throw new HibernateException( "Improper set up of DataSourceBasedMultiTenantConnectionProviderImpl" ); } ...{noformat} The changed behavior is that the the parameter is no longer a String, but a WildFlyDataSource. I'm opening this case just to check if this is the expected behavior, and I should really override the necessary part of the code in order to circumvent the error or was this some sort of regression? Kindly, Rafael Sampaio -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5448) Prepare PMML for Transformations implementation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5448?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5448: ------------------------------------- Description: Add TransformationDictionary parameter to compiler methods to have it available for actual Transformation management. Setup the main flow for actual transformations usage was: Add TransformationDictionary parameter to compiler methods to have it available for actual Transformation management > Prepare PMML for Transformations implementation > ----------------------------------------------- > > Key: DROOLS-5448 > URL: https://issues.redhat.com/browse/DROOLS-5448 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Add TransformationDictionary parameter to compiler methods to have it available for actual Transformation management. > Setup the main flow for actual transformations usage -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5448) Add "TransformationDictionary" to signatures

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5448?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5448: ------------------------------------- Description: Add TransformationDictionary parameter to compiler methods to have it available for actual Transformation management was: Add TransformationDictionary parameter to compiler methods to have ti available for actual Transformation management > Add "TransformationDictionary" to signatures > -------------------------------------------- > > Key: DROOLS-5448 > URL: https://issues.redhat.com/browse/DROOLS-5448 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Add TransformationDictionary parameter to compiler methods to have it available for actual > Transformation management -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5448) Prepare PMML for Transformations implementation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5448?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5448: ------------------------------------- Summary: Prepare PMML for Transformations implementation (was: Add "TransformationDictionary" to signatures) > Prepare PMML for Transformations implementation > ----------------------------------------------- > > Key: DROOLS-5448 > URL: https://issues.redhat.com/browse/DROOLS-5448 > Project: Drools > Issue Type: Sub-task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Add TransformationDictionary parameter to compiler methods to have it available for actual > Transformation management -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5448) Add "TransformationDictionary" to signatures

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5448: ---------------------------------------- Summary: Add "TransformationDictionary" to signatures Key: DROOLS-5448 URL: https://issues.redhat.com/browse/DROOLS-5448 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Add TransformationDictionary parameter to compiler methods to have ti available for actual Transformation management -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5435) Create kie-pmml-trusty dependencies pom

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5435?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5435. ------------------------------------ > Create kie-pmml-trusty dependencies pom > --------------------------------------- > > Key: DROOLS-5435 > URL: https://issues.redhat.com/browse/DROOLS-5435 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Create a maven "pom" module that defines all the kie-pmml-new dependencies. > Such module should import kie-pmml-bom (for dependencyManagement) and declare all the kie-pmml-trusty modules. > Then, client module would just need to declare such pom as dependency (with "pom" type) > e.g. > > <dependencies> > ... > <dependency> > <dependency> > <groupId>org.kie</groupId> > <artifactId>kie-pmml-dependencies</artifactId> > <type>pom</type> > </dependency> > </dependency> > </dependencies> -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5435) Create kie-pmml-trusty dependencies pom

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5435?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5435: ------------------------------------- Git Pull Request: https://github.com/kiegroup/drools/pull/2960 (was: https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1372) > Create kie-pmml-trusty dependencies pom > --------------------------------------- > > Key: DROOLS-5435 > URL: https://issues.redhat.com/browse/DROOLS-5435 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Create a maven "pom" module that defines all the kie-pmml-new dependencies. > Such module should import kie-pmml-bom (for dependencyManagement) and declare all the kie-pmml-trusty modules. > Then, client module would just need to declare such pom as dependency (with "pom" type) > e.g. > > <dependencies> > ... > <dependency> > <dependency> > <groupId>org.kie</groupId> > <artifactId>kie-pmml-dependencies</artifactId> > <type>pom</type> > </dependency> > </dependency> > </dependencies> -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1187) Workloads list test - Add back labels comparison

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1187?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1187: ------------------------------------- Assignee: Hayk Hovsepyan > Workloads list test - Add back labels comparison > ------------------------------------------------ > > Key: SWSQE-1187 > URL: https://issues.redhat.com/browse/SWSQE-1187 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Label comparison between OC and UI. > In Workloads lists test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 June 2020