-
Bug
-
Resolution: Done
-
Blocker
-
36.0.1.Final
-
None
-
-
---
-
---
There is a regression caused by Wildfly http-client 2.0.7.Final -> 2.1.0.Final upgrade.
Test which is trying JNDI lookup over Undertow configured as load balancer fails with:
javax.naming.CommunicationException: WFHTTP000005: Invalid response code 404 (full response ClientResponse{responseHeaders={content-length=[74], content-type=[text/html], date=[Mon, 02 Jun 2025 12:18:22 GMT]}, responseCode=404, status='', protocol=HTTP/2.0}) [Root exception is java.io.IOException: WFHTTP000005: Invalid response code 404 (full response ClientResponse{responseHeaders={content-length=[74], content-type=[text/html], date=[Mon, 02 Jun 2025 12:18:22 GMT]}, responseCode=404, status='', protocol=HTTP/2.0})]
at org.wildfly.httpclient.naming.HttpRootContext.performOperation(HttpRootContext.java:291)
at org.wildfly.httpclient.naming.HttpRootContext.lambda$processInvocation$1(HttpRootContext.java:248)
at org.wildfly.httpclient.naming.HttpRootContext.performWithRetry(HttpRootContext.java:176)
at org.wildfly.httpclient.naming.HttpRootContext.processInvocation(HttpRootContext.java:241)
at org.wildfly.httpclient.naming.HttpRootContext.processInvocation(HttpRootContext.java:231)
at org.wildfly.httpclient.naming.HttpRootContext.lookupNative(HttpRootContext.java:118)
at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:84)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
at org.jboss.qa.artemis.test.loadbalancers.ClusterFrontEndLoadBalancingTestCase.jndiLookupBehindBalancer(ClusterFrontEndLoadBalancingTestCase.java:530)
- is blocked by
-
WFLY-20698 Upgrade WildFly HTTP Client to 2.1.1.Final
-
- Resolved
-
- is caused by
-
WEJBHTTP-139 Refactor WildFly HTTP Client in order to be easily extensible
-
- Resolved
-
- is cloned by
-
JBEAP-30324 404 error on JNDI lookup behind load balancer
-
- Verified
-