WildFly/Undertow: Undertow WebSocket does not work in WildFly Arquillian test

Question

Currently, I am trying to update the eclipse-ee4j/cargotracker(originally it is a rewritten version of the Eric's DDD book sample) to the latest Jakarta EE 8:

https://github.com/hantsy/cargotracker/tree/jakartaee8

I was trying to test WebSocket endpoint(/tracking) against the latest WildFly 22.0.0.Final, WildFly Arquillian 3.0.1.Final, and Arquillian Core 1.6.0.

Like testing Jaxrs with jaxrs client, and tried to add Undertow websocket jsr as deps to use the built-in WebSocket client API to test websocket endpoint.

<dependency>
    <groupId>io.undertow</groupId>
    <artifactId>undertow-websockets-jsr</artifactId>
    <version>2.2.3.Final</version>
    <scope>test</scope>
</dependency>
<dependency>
    <groupId>org.jboss.threads</groupId>
    <artifactId>jboss-threads</artifactId>
    <version>2.4.0.Final</version>
    <scope>test</scope>
</dependency>

The version of the above deps are same as the ones in the WildFly 22.0.0.Final.

The undertow-WebSockets-jsr required JBoss threads when running the test, it failed due to an arquillain lifecycle error, the aruqillain did not start deployment work at all.

My question is if using the WildFly facilities, which deps are required correctly for WebSocket tests.

As a workaround, currently I switched to use Glassfish tyrus client to make my tests passed.

question from:https://stackoverflow.com/questions/65881993/wildfly-undertow-undertow-websocket-does-not-work-in-wildfly-arquillian-test

Answer 1

Waitting for answers