[Red Hat JIRA] (WFLY-12881) Cannot customize split behavior and merge policy for Infinispan partition handling
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12881:
------------------------------------
Fix Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
> Cannot customize split behavior and merge policy for Infinispan partition handling
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12881
> URL: https://issues.redhat.com/browse/WFLY-12881
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 18.0.1.Final, 19.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 22.0.0.Beta1
>
>
> Currently, partition handling of an Infinispan cache is hard coded. When enabled, both reads and writes are denied on minority partitions (of a given segment) and, more critically, upon partition merge, no reconciliation of any data conflicts occurs.
> Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-13802) The undertow layer can not deploy deployments without the ee layer
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13802?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13802:
------------------------------------
Fix Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
> The undertow layer can not deploy deployments without the ee layer
> ------------------------------------------------------------------
>
> Key: WFLY-13802
> URL: https://issues.redhat.com/browse/WFLY-13802
> Project: WildFly
> Issue Type: Bug
> Components: Build System, Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 22.0.0.Beta1
>
>
> {code:java}
> 16:35:06,234 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> 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)
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50)
> at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:709)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:276)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-13706) Support a Galleon feature pack to install Keycloak adapters
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13706?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13706:
------------------------------------
Fix Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
> Support a Galleon feature pack to install Keycloak adapters
> -----------------------------------------------------------
>
> Key: WFLY-13706
> URL: https://issues.redhat.com/browse/WFLY-13706
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation, Security, Test Suite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 22.0.0.Beta1
>
>
> In conjunction with the bootable jar support currently being developed this feature request is to cover support for Keycloak client side adapter installation integrated with the Elytron security subsystem.
> The main feature pack is anticipated to be delivered by the Keycloak project, however as this is specifically for use with WildFly we likely need WildFly documentation and possibly test cases so this Jira issue to to cover tasks required within WildFly.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-13655) LOG INFO level message if the Hibernate second level cache is enabled
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13655?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13655:
------------------------------------
Fix Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
> LOG INFO level message if the Hibernate second level cache is enabled
> ---------------------------------------------------------------------
>
> Key: WFLY-13655
> URL: https://issues.redhat.com/browse/WFLY-13655
> Project: WildFly
> Issue Type: Enhancement
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Minor
> Fix For: 22.0.0.Beta1
>
>
> The idea is to log at INFO level if the Hibernate second level cache is to be enabled by org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator. Note that org.hibernate.cache.internal.RegionFactoryInitiator#resolveRegionFactory still needs to be able to create the second level cache.
> Update WildFlyCustomRegionFactoryInitiator#resolveRegionFactory to log at INFO level the "WildFlyCustomRegionFactoryInitiator#resolveRegionFactory will create second level cache %s" message.
> This message will only be logged during application deployment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13871:
------------------------------------
Fix Version/s: 22.0.0.Beta1
(was: 21.0.0.Final)
> Re-implement correct suspend/resume behaviour for EJB client
> ------------------------------------------------------------
>
> Key: WFLY-13871
> URL: https://issues.redhat.com/browse/WFLY-13871
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Labels: downstream_dependency
> Fix For: 22.0.0.Beta1
>
>
> When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations.
> This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored.
> This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months