[JBoss JIRA] (WFCORE-5133) SNICombinedWithALPNTestCase fails with oracle JDK 8 261
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/WFCORE-5133?page=com.atlassian.jira.plug... ]
Sonia Zaldana commented on WFCORE-5133:
---------------------------------------
I am removing myself from this issue, as it seems like it is a larger issue than originally expected and we are waiting for input from Flavia. I would be happy to reassign myself if my help is needed.
> SNICombinedWithALPNTestCase fails with oracle JDK 8 261
> -------------------------------------------------------
>
> Key: WFCORE-5133
> URL: https://issues.redhat.com/browse/WFCORE-5133
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jean Francois Denise
> Assignee: Darran Lofthouse
> Priority: Major
>
> Exception while using oracle JDK 261:
>
> {code}
> at io.undertow.client.http.HttpClientConnection.handleError(HttpClientConnection.java:444)
> at io.undertow.client.http.HttpClientConnection.handleError(HttpClientConnection.java:439)
> at io.undertow.client.http.HttpClientConnection.initiateRequest(HttpClientConnection.java:430)
> at io.undertow.client.http.HttpClientConnection.sendRequest(HttpClientConnection.java:347)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase.performSimpleTest(SNICombinedWithALPNTestCase.java:242)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase.testSimpleViaHostname(SNICombinedWithALPNTestCase.java:220)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-5133) SNICombinedWithALPNTestCase fails with oracle JDK 8 261
by Sonia Zaldana (Jira)
[ https://issues.redhat.com/browse/WFCORE-5133?page=com.atlassian.jira.plug... ]
Sonia Zaldana reassigned WFCORE-5133:
-------------------------------------
Assignee: Darran Lofthouse (was: Sonia Zaldana)
> SNICombinedWithALPNTestCase fails with oracle JDK 8 261
> -------------------------------------------------------
>
> Key: WFCORE-5133
> URL: https://issues.redhat.com/browse/WFCORE-5133
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jean Francois Denise
> Assignee: Darran Lofthouse
> Priority: Major
>
> Exception while using oracle JDK 261:
>
> {code}
> at io.undertow.client.http.HttpClientConnection.handleError(HttpClientConnection.java:444)
> at io.undertow.client.http.HttpClientConnection.handleError(HttpClientConnection.java:439)
> at io.undertow.client.http.HttpClientConnection.initiateRequest(HttpClientConnection.java:430)
> at io.undertow.client.http.HttpClientConnection.sendRequest(HttpClientConnection.java:347)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase.performSimpleTest(SNICombinedWithALPNTestCase.java:242)
> at org.jboss.as.test.integration.security.ssl.sni.SNICombinedWithALPNTestCase.testSimpleViaHostname(SNICombinedWithALPNTestCase.java:220)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13925) Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13925?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13925:
-----------------------------------------
Shouldn't that dependency be 'provided' scope? JaxrsDependencyProcessor will add that dep to the deployment classpath if the module is present.
> Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13925
> URL: https://issues.redhat.com/browse/WFLY-13925
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client, Web (Undertow)
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Stefanko
> Priority: Major
>
> This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13925) Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
by r searls (Jira)
[ https://issues.redhat.com/browse/WFLY-13925?page=com.atlassian.jira.plugi... ]
r searls updated WFLY-13925:
----------------------------
Description:
This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
was:
This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
Quoting [~rsearls]:
This appears to be an issue in wfly deployment processing.
I can confirm when deploying the app that contains resteasy-client-microprofile
the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
When the app does not contain resteasy-client-microprofile the servlet executed
by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
when the app contains resteasy-client-microprofile and value
ServletInfo{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
when it does not.
In wfly I looked at the jaxrs deployment code. I can see that for both
apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
but when resteasy-client-microprofile is present some wfly process that runs after
jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
> Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13925
> URL: https://issues.redhat.com/browse/WFLY-13925
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client, Web (Undertow)
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Stefanko
> Priority: Major
>
> This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13925) Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
by r searls (Jira)
[ https://issues.redhat.com/browse/WFLY-13925?page=com.atlassian.jira.plugi... ]
r searls updated WFLY-13925:
----------------------------
Description:
This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
Quoting [~rsearls]:
This appears to be an issue in wfly deployment processing.
I can confirm when deploying the app that contains resteasy-client-microprofile
the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
When the app does not contain resteasy-client-microprofile the servlet executed
by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
when the app contains resteasy-client-microprofile and value
ServletInfo{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
when it does not.
In wfly I looked at the jaxrs deployment code. I can see that for both
apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
but when resteasy-client-microprofile is present some wfly process that runs after
jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
was:
Quoting [~rsearls]:
This appears to be an issue in wfly deployment processing.
I can confirm when deploying the app that contains resteasy-client-microprofile
the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
When the app does not contain resteasy-client-microprofile the servlet executed
by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
when the app contains resteasy-client-microprofile and value
ServletInfo\{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
when it does not.
In wfly I looked at the jaxrs deployment code. I can see that for both
apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
but when resteasy-client-microprofile is present some wfly process that runs after
jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
Steps to Reproduce:
The test case is here
https://github.com/rsearls/WFLY-13925-testcase.git
Case 1, the successful case.
build this project
deploy the app to wildfly-21.0.0.Beta1-SNAPSHOT
Use cURL to call the endpoint
curl -v http://localhost:8080/rest-client-wfly/ping
Case 2, the unsuccessful case.
Edit pom.xml and uncomment archive org.jboss.resteasy:resteasy-client-microprofile
build this project
deploy the app to wildfly-21.0.0.Beta1-SNAPSHOT
Use cURL to call the endpoint
curl -v http://localhost:8080/rest-client-wfly/ping
Quoting [~rsearls]:
This appears to be an issue in wfly deployment processing.
I can confirm when deploying the app that contains resteasy-client-microprofile
the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
When the app does not contain resteasy-client-microprofile the servlet executed
by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
when the app contains resteasy-client-microprofile and value
ServletInfo{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
when it does not.
In wfly I looked at the jaxrs deployment code. I can see that for both
apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
but when resteasy-client-microprofile is present some wfly process that runs after
jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
> Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13925
> URL: https://issues.redhat.com/browse/WFLY-13925
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client, Web (Undertow)
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Stefanko
> Priority: Major
>
> This project defines a simple REST endpoint. When the archive is built and deployed without archive org.jboss.resteasy:resteasy-client-microprofile (see pom.xml lines 18-22) the endpoint can be reached successfully. When the archive is built and deployed with org.jboss.resteasy:resteasy-client-microprofile the endpoint can not be reached.
>
>
>
>
> Quoting [~rsearls]:
>
> This appears to be an issue in wfly deployment processing.
> I can confirm when deploying the app that contains resteasy-client-microprofile
> the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
> When the app does not contain resteasy-client-microprofile the servlet executed
> by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
> Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
> line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
> when the app contains resteasy-client-microprofile and value
> ServletInfo{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
> when it does not.
> In wfly I looked at the jaxrs deployment code. I can see that for both
> apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
> but when resteasy-client-microprofile is present some wfly process that runs after
> jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13925) Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
by r searls (Jira)
[ https://issues.redhat.com/browse/WFLY-13925?page=com.atlassian.jira.plugi... ]
r searls updated WFLY-13925:
----------------------------
Component/s: Web (Undertow)
(was: REST)
> Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13925
> URL: https://issues.redhat.com/browse/WFLY-13925
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client, Web (Undertow)
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Stefanko
> Priority: Major
>
> Quoting [~rsearls]:
>
> This appears to be an issue in wfly deployment processing.
> I can confirm when deploying the app that contains resteasy-client-microprofile
> the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
> When the app does not contain resteasy-client-microprofile the servlet executed
> by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
> Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
> line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
> when the app contains resteasy-client-microprofile and value
> ServletInfo\{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
> when it does not.
> In wfly I looked at the jaxrs deployment code. I can see that for both
> apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
> but when resteasy-client-microprofile is present some wfly process that runs after
> jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13925) Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
by r searls (Jira)
[ https://issues.redhat.com/browse/WFLY-13925?page=com.atlassian.jira.plugi... ]
r searls reassigned WFLY-13925:
-------------------------------
Assignee: (was: r searls)
> Deployment with the `resteasy-client-microprofile` dependency causes JAX-RS endpoints to not be exposed
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13925
> URL: https://issues.redhat.com/browse/WFLY-13925
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client, REST
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Stefanko
> Priority: Major
>
> Quoting [~rsearls]:
>
> This appears to be an issue in wfly deployment processing.
> I can confirm when deploying the app that contains resteasy-client-microprofile
> the servlet executed by undertow is io.undertow.servlet.handlers.DefaultServlet.
> When the app does not contain resteasy-client-microprofile the servlet executed
> by undertow is org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher.
> Setting a breakpoint in io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy
> line 300, method start() you will see ServletInfo\{mappings=[], servletClass=class io.undertow.servlet.handlers.DefaultServlet, name='default'}
> when the app contains resteasy-client-microprofile and value
> ServletInfo\{mappings=[/*], servletClass=class org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher, name='io.xstefank.RestApplication'}
> when it does not.
> In wfly I looked at the jaxrs deployment code. I can see that for both
> apps, servletClass is assigned org.jboss.resteasy.plugins.server.servlet.HttpServlet30Dispatcher
> but when resteasy-client-microprofile is present some wfly process that runs after
> jaxrs overwrites this information with servletClass=class io.undertow.servlet.handlers.DefaultServlet.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (JGRP-2504) Poor throughput over high latency TCP connection when recv_buf_size is configured
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2504?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2504:
--------------------------------
Taking me a little longer; I'm taking the opportunity for some refactoring.
> Poor throughput over high latency TCP connection when recv_buf_size is configured
> ---------------------------------------------------------------------------------
>
> Key: JGRP-2504
> URL: https://issues.redhat.com/browse/JGRP-2504
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 5.0.0.Final
> Reporter: Andrew Skalski
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.1
>
> Attachments: SpeedTest.java, bla5.java, bla6.java, bla7.java, delay-ip.sh
>
>
> I recently finished troubleshooting a unidirectional throughput bottleneck involving a JGroups application (Infinispan) communicating over a high-latency (~45 milliseconds) TCP connection.
> The root cause was JGroups improperly configuring the receive/send buffers on the listening socket. According to the tcp(7) man page:
> {code:java}
> On individual connections, the socket buffer size must be set prior to
> the listen(2) or connect(2) calls in order to have it take effect.
> {code}
> However, JGroups does not set the buffer size on the listening side until after accept().
> The result is poor throughput when sending data from client (connecting side) to server (listening side.) Because the issue is a too-small TCP receive window, throughput is ultimately latency-bound.
--
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 Jan Stourac (Jira)
[ https://issues.redhat.com/browse/WFLY-13924?page=com.atlassian.jira.plugi... ]
Jan Stourac commented on WFLY-13924:
------------------------------------
Thanks for the mention, Darran. I've put WF21 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