[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, 2 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, 2 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 commented on WFLY-13802:
-----------------------------------------
[~dlofthouse] This is going to roll over to WF 22 although the specific issue is fixed, as there is some ongoing discussion. If you'd prefer to resolve this for WF 21, please feel free to do so. The release notes are dynamic so adding things after the fact is fine.
> 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: 21.0.0.Final
>
>
> {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, 2 months