-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
-
Regression, Blocks Testing
-
-
-
-
-
-
-
Rejected
-
-
This issue is a regression against EAP 8.0.0.CR1. I checked this issue on testing build, which is based on CR2 tag. This issue is caused by wildfly-http-client upgrade from version 2.0.2.Final-redhat-00001 to version 2.0.5.Final-redhat-00001. This issue is valid only for http/https connectors.
The following exception is thrown during bean invocations:
java.io.IOException: WFHTTP000005: Invalid response code 404 (full response ClientResponse{responseHeaders={content-length=[74], content-type=[text/html], date=[Wed, 08 Nov 2023 09:37:22 GMT]}, responseCode=404, status='', protocol=HTTP/2.0})
at org.wildfly.httpclient.common.HttpTargetContext$2$1.lambda$completed$4(HttpTargetContext.java:245)
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 org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282)
at java.base/java.lang.Thread.run(Thread.java:834)
Reproducer:
This issue can be reproduced by upstream EJB TS:
EAP_HOME=/path/to/eap
mvn -DspecificModule=basic -Dmaven.test.failure.ignore=true -Dconnector=http -Dcontext.type=wildfly-naming-client -Dauthentication.type=user -Dserver.home=${EAP_HOME} -DgroupId.ee.bom=org.jboss.bom -DartifactId.ee.bom=jboss-eap-ee -Dversion.ee.bom=8.0.0.GA-redhat-20231106 -DgroupId.ejb.client.bom=org.jboss.eap -DartifactId.ejb.client.bom=wildfly-ejb-client-bom -Dversion.ejb.client.bom=8.0.0.GA-redhat-20231106 test -Dtest=WhoAmITestCase#isCallerInRole
If you replace wildfly-http-client in server by older version (2.0.2.Final-redhat-00001), the issue disappear.
Anyway more tests are affected, specifically those:
WhoAmITestCase WhoAmI_Stateful_TestCase ExecuteInWorkerTestCase LambdaTestCase SingletonEchoTestCase StatefulEchoTestCase StatelessEchoTestCase AsyncSingletonEchoTestCase AsyncStatefulEchoTestCase AsyncStatelessEchoTestCase SetSourceIpAddressTestCase#testHostBindingStandaloneClient AnnotationIndexTestCase#tryInvokeEJBFromClient BeanPoolWithShortTimeoutTestCase#slsbWithPoolSize1AndShortTimeout ConcurrentStatefulProxyUsageTestCase#test EarWithMoreThan64EJBSubdeploymentsTestCase#test GracefulShutdownConnectorsTestCase#testGracefulShutdown TimerServiceGracefulShutdownTestCase#testThatTimersDontGoOffAfterSuspend MultipleResourcesByOneContextTestCase#testMultipleServices
With respect to the fact that high number of tests are affected, this issue could hide another product issues.
- is caused by
-
-
- Resolved
-
- is cloned by
-
-
- Closed
-
- is incorporated by
-
JBEAP-26048 Upgrade WildFly Http Client to 2.0.6.Final
-
- Closed
-
