[JBoss JIRA] (WFLY-13942) Drop support for Hibernate 4 modules
by Sanne Grinovero (Jira)
Sanne Grinovero created WFLY-13942:
--------------------------------------
Summary: Drop support for Hibernate 4 modules
Key: WFLY-13942
URL: https://issues.redhat.com/browse/WFLY-13942
Project: WildFly
Issue Type: Task
Components: JPA / Hibernate
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
The modules for Hibernate5-legacy have already been removed (WFLY-13819), we should cleanup the support for Hibernate 4 as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-408) Add a TRACE level category for the operations used to start a server.
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-408?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-408:
-----------------------------------------
The need may have been dropped a bit TBH moving to persistent resource definitions has helped with a lot of the mismatch type problems we used to have - I wouldn't worry too much about this one now.
> Add a TRACE level category for the operations used to start a server.
> ---------------------------------------------------------------------
>
> Key: WFCORE-408
> URL: https://issues.redhat.com/browse/WFCORE-408
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Logging, Management
> Reporter: Darran Lofthouse
> Priority: Major
>
> Sometimes after being able to start a server from the XML configuration it is useful to be able to identify the actual operations that are executed to start the server.
> From a development perspective this is useful for double checking the operations are as we expect.
> From an end user perspective this can be useful to identify the set of equivalent operations needed if the same was to be achieved in a CLI script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13924) HTTP2 is not working with Oracle JDK8 u261
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13924?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFLY-13924:
-----------------------------------------
A thread titled ELY-2026 has been started in the #wildfly-elytron stream in Zulip, the discussions on the thread cover both the Elytron fix and the changes needed in Undertow so lets please continue the discussion over there.
> HTTP2 is not working with Oracle JDK8 u261
> ------------------------------------------
>
> Key: WFLY-13924
> URL: https://issues.redhat.com/browse/WFLY-13924
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Affects Versions: 20.0.0.Final, 20.0.1.Final, 21.0.0.Beta1
> Reporter: Jan Stourac
> Assignee: Flavia Rainone
> Priority: Blocker
> Fix For: 21.0.0.Final
>
>
> There seems to be some problem with HTTP2 support with new Oracle JDK8 u261 and WildFly since {{20.0.0.Final}} version. When request against server is executed, then HTTP2 is not established and communication remains via HTTP/1.1.
> There is no such issue when I use {{WildFly 19.0.0.Final}}. Also, if I switch back to an older Oracle JDK8 u241, there is no such issue even with newer WildFly versions.
> This all seems to be tied with backport of ALPN support into the Oracle JDK8 recently and also work in following issue UNDERTOW-1726.
> There seems to be a workaround available - to define '-Dio.undertow.protocols.alpn.jdk8' during the server startup. With this property configured, the issue seems to disappear (as such, blocker priority of this may be discussed).
> *What is the issue here:*
> This is a change in default behavior of the server (HTTP2 not working with Oracle JDK8u261+ since WildFly 20.0.0.Final). We should try to resolve this without default behavior change if possible. Only in case there is really no other solution, we need to document such thing.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months