[JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10134:
------------------------------------
We discussed this in chat. The servlet classes are loaded later, but the module is indeed loaded earlier from JACC as Brian suspected.
No solution has yet presented itself.
> ee8.preview.mode property is racy
> ---------------------------------
>
> Key: WFLY-10134
> URL: https://issues.jboss.org/browse/WFLY-10134
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Reporter: David Lloyd
> Priority: Critical
>
> The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded. This assumption appears to be invalid.
> System properties are installed by the boot controller thread, and extensions are loaded in server service threads. In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads. I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless.
> Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10146) Clean up CMTTxInterceptor
by David Lloyd (JIRA)
David Lloyd created WFLY-10146:
----------------------------------
Summary: Clean up CMTTxInterceptor
Key: WFLY-10146
URL: https://issues.jboss.org/browse/WFLY-10146
Project: WildFly
Issue Type: Task
Components: EJB
Reporter: David Lloyd
Assignee: David Lloyd
There are a lot of issues with CMTTxInterceptor which make the code hard to read, hard to debug, and hard to modify.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-2930) Support a socket-binding-group as a child of profile
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2930?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-2930:
----------------------------------------
Fix Version/s: (was: 5.0.0.Alpha3)
Assignee: (was: Brian Stansberry)
> Support a socket-binding-group as a child of profile
> ----------------------------------------------------
>
> Key: WFCORE-2930
> URL: https://issues.jboss.org/browse/WFCORE-2930
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Priority: Critical
>
> Allow a single socket-binding-group resource as a child of profile, such that resolution of bindings from the subsystems are limited to the s-b-g associated with the profile.
> A server-group that uses such a profile cannot reference a socket-binding-group. And a server in that server-group cannot reference an s-b-g to override the one from the server-group/profile.
> I'm not sure how the s-b-g resource will work. Perhaps the resource would go away under 'profile' with the bindings direct children of profile. The 'default-interface' attribute then becomes an attribute of profile. Or perhaps there will be an s-b-g resource, but with a fixed name that's the same as the profile. Currently I think the latter.
> This will be necessary for resolution of config elements using the upcoming provisioning tool. The tool will not be able to do correct "feature" resolution using the complex rules we currently support.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10020) Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10020?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10020:
-------------------------------------
We are trying to get this done for WildFly 13. Some of the related code is in Hibernate ORM (master branch) and some will be in the Infinispan project as well.
In terms of keeping an eye on the effort, when it comes together, it should show up in [https://github.com/wildfly/wildfly].
> Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10020
> URL: https://issues.jboss.org/browse/WFLY-10020
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Migrating to 12 with Hibernate Custom slot causes NullPointer Exception.
> https://mvnrepository.com/artifact/org.hibernate/hibernate-orm-modules
> <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.13.Final" />
> 16:12:28,868 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for optoplus
> 16:12:29,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "optoplus-services-ear-1.0.18-SNAPSHOT.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.secondLevelCache.InfinispanCacheDeploymentListener.addCacheDependencies(InfinispanCacheDeploymentListener.java:129)
> at org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener.addCacheDependencies(CacheDeploymentListener.java:111)
> at org.jipijapa.event.impl.internal.Notification.addCacheDependencies(Notification.java:95)
> at org.jboss.as.jpa.hibernate5.HibernateSecondLevelCache.addSecondLevelCacheDependencies(HibernateSecondLevelCache.java:125)
> at org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(HibernatePersistenceProviderAdaptor.java:107)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:538)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:273)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> 16:12:29,155 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"optoplus-services-ear-1.0.18-SNAPSHOT.ear\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"optoplus-services-ear-1.0.18-SNAPSHOT.ear\"
> Caused by: java.lang.NullPointerException"}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10020) Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
by Alessandro Moscatelli (JIRA)
[ https://issues.jboss.org/browse/WFLY-10020?page=com.atlassian.jira.plugin... ]
Alessandro Moscatelli commented on WFLY-10020:
----------------------------------------------
Ok, thank you for your answer.
To be accurate, what release 2lc support depends on (what should I keep my eyes opened on) ?
When everything will be ready wildfly 12 hibernate-orm-modules will be published ?
> Custom Hibernate slot and second level cache with Wildfly 12 causes NullPointer Exception
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10020
> URL: https://issues.jboss.org/browse/WFLY-10020
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 12.0.0.Final
> Reporter: Alessandro Moscatelli
> Assignee: Scott Marlow
>
> Migrating to 12 with Hibernate Custom slot causes NullPointer Exception.
> https://mvnrepository.com/artifact/org.hibernate/hibernate-orm-modules
> <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2.13.Final" />
> 16:12:28,868 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for optoplus
> 16:12:29,142 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."optoplus-services-ear-1.0.18-SNAPSHOT.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "optoplus-services-ear-1.0.18-SNAPSHOT.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.jpa.processor.secondLevelCache.InfinispanCacheDeploymentListener.addCacheDependencies(InfinispanCacheDeploymentListener.java:129)
> at org.jboss.as.jpa.processor.secondLevelCache.CacheDeploymentListener.addCacheDependencies(CacheDeploymentListener.java:111)
> at org.jipijapa.event.impl.internal.Notification.addCacheDependencies(Notification.java:95)
> at org.jboss.as.jpa.hibernate5.HibernateSecondLevelCache.addSecondLevelCacheDependencies(HibernateSecondLevelCache.java:125)
> at org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.addProviderDependencies(HibernatePersistenceProviderAdaptor.java:107)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:538)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:273)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135)
> at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more
> 16:12:29,155 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"optoplus-services-ear-1.0.18-SNAPSHOT.ear\".FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"optoplus-services-ear-1.0.18-SNAPSHOT.ear\"
> Caused by: java.lang.NullPointerException"}}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3382) Further Enhance Elytron Permission Configuration
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3382?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-3382:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
(was: 5.0.0.Alpha2)
> Further Enhance Elytron Permission Configuration
> ------------------------------------------------
>
> Key: WFCORE-3382
> URL: https://issues.jboss.org/browse/WFCORE-3382
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Security
> Reporter: Darran Lofthouse
> Priority: Blocker
> Fix For: 5.0.0.Alpha3
>
>
> This has currently been simplified to a single resource for the out of the box configuration, however this brings issues as now permissions are duplicated so modifications need to be replicated instead of to a single location.
> Finding a way for the default required permissions to be defined in one location could help eliminate the duplication.
> We could also consider going one step further and subsystems register the default permissions that should be granted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month