[Red Hat JIRA] (WFLY-14077) Some tests hang indefinitely when using security manager on JDK 11.0.8 & JDK 11.0.9
by Ondrej Kotek (Jira)
[ https://issues.redhat.com/browse/WFLY-14077?page=com.atlassian.jira.plugi... ]
Ondrej Kotek reopened WFLY-14077:
---------------------------------
This is still valid for Open|Oracle JDK 11.0.10.
Is this really just a test issue that can be solved by adding the missing permission?
{{org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase}} seems also affected (the same missing permission when loading {{org.jboss.marshalling.river.Protocol}}).
> Some tests hang indefinitely when using security manager on JDK 11.0.8 & JDK 11.0.9
> -----------------------------------------------------------------------------------
>
> Key: WFLY-14077
> URL: https://issues.redhat.com/browse/WFLY-14077
> Project: WildFly
> Issue Type: Task
> Components: Security Manager
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Richard Opalka
> Priority: Major
> Attachments: stacktrace.log
>
>
> Some tests hang indefinitely when using security manager and JDK 11 : e.g. AuthenticationForwardingSFSFTestCase.java , AuthenticationForwardingSLSFTestCase.java
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-14411) [Bootable JAR] server components and Galleon FP upgrade
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-14411?page=com.atlassian.jira.plugi... ]
Jean Francois Denise moved EAP7-1640 to WFLY-14411:
---------------------------------------------------
EAP PT Analysis Document (AD): (was: TODO)
EAP PT Community Docs (CD): (was: TODO)
EAP PT Docs Analysis (DA): (was: TODO)
EAP PT Feature Implementation (FI): (was: TODO)
EAP PT Pre-Checked (PC): (was: TODO)
EAP PT Product Docs (PD): (was: New)
EAP PT Test Dev (TD): (was: TODO)
EAP PT Test Plan (TP): (was: TODO)
Key: WFLY-14411 (was: EAP7-1640)
Target Release: (was: EAP-XP-3.0.0.GA)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Issue Type: Feature Request (was: Requirement)
Project: WildFly (was: JBoss EAP Planning for version 7 and above)
> [Bootable JAR] server components and Galleon FP upgrade
> -------------------------------------------------------
>
> Key: WFLY-14411
> URL: https://issues.redhat.com/browse/WFLY-14411
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Jean Francois Denise
> Assignee: Jean Francois Denise
> Priority: Major
>
> We have a need to be able to upgrade the server components present in a Bootable JAR when building the jar from the Bootable JAR maven plugin.
> 2 kind of items can be upgraded:
> * JBoss Modules module jar files (eg: undertow-core).
> * EAP 7.4.x Galleon feature-pack that is a dependency of the XP 3.0.x Galleon feature-pack.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-13693) Custom Infinispan cache regions fail when using legacy (non-JPA) Hibernate configuration
by Stephen Fikes (Jira)
[ https://issues.redhat.com/browse/WFLY-13693?page=com.atlassian.jira.plugi... ]
Stephen Fikes closed WFLY-13693.
--------------------------------
Resolution: Explained
Resolution was to add {{<property name="hibernate.cache.infinispan.shared">false</property>}} to the legacy Hibernate configuration ({{hibernate.cfg.xml}}).
> Custom Infinispan cache regions fail when using legacy (non-JPA) Hibernate configuration
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-13693
> URL: https://issues.redhat.com/browse/WFLY-13693
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final, 18.0.0.Final
> Reporter: Stephen Fikes
> Assignee: Scott Marlow
> Priority: Major
>
> A custom cache template is defined in the "hibernate" cache container in the {{standalone.xml}}
> {code:java}
> <local-cache name="entities.custom-cache">
> <transaction mode="NONE"/>
> <object-memory size="10"/>
> </local-cache>
> {code}
> In the legacy {{hibernate.cfg.xml}} this is associated with a named cache region.
> {code:java}
> <property name="hibernate.cache.region_prefix">entities</property>
> <property name="hibernate.cache.infinispan.entities.custom-cache.cfg">entities.custom-cache</property>
> <property name="hibernate.cache.use_second_level_cache">true</property>
> {code}
> The cache region is then referenced in an entity annotation:
> {code:java}
> @Entity
> @Cache(usage=CacheConcurrencyStrategy.READ_WRITE, region="custom-cache")
> public class Employee {
> ...
> }
> {code}
> At deployment, an exception is logged:
> {noformat}
> ... HHH025007: Custom cache configuration 'entities.custom-cache' was requested for region entities.custom-cache but it was not found - using configuration by type (entity).
> {noformat}
> This same approach (but using transactional caching) worked in Wildfly 11.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 2 months
[Red Hat JIRA] (WFLY-13617) Hibernate DataSourceBasedMultiTenantConnectionProviderImpl does not work for Multitenancy
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-13617?page=com.atlassian.jira.plugi... ]
Scott Marlow resolved WFLY-13617.
---------------------------------
Resolution: Migrated to another ITS
https://hibernate.atlassian.net/browse/HHH-14448 is the proper issue for the exception that you are seeing. If the problem can be fixed, I think it would be best to investigate doing so for the Hibernate ORM project.
> 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
(v8.13.1#813001)
5 years, 2 months