Wildfly运行超时但服务器已启动，Maven集成测试配置排查求助

Hey there! Let's dig into this WildFly timeout issue you're facing—even though deployment looks successful, those timeouts can be tricky. Here are some common configurations you might have missed:

Integration tests typically rely on the maven-failsafe-plugin, and its default timeout window might be too short for your app's initialization. Check your pom.xml to extend this:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-failsafe-plugin</artifactId>
    <version>3.2.5</version>
    <configuration>
        <!-- Extend timeout to 5 minutes (adjust as needed) -->
        <forkedProcessTimeoutInSeconds>300</forkedProcessTimeoutInSeconds>
        <reuseForks>false</reuseForks>
    </configuration>
    <executions>
        <execution>
            <goals>
                <goal>integration-test</goal>
                <goal>verify</goal>
            </goals>
        </execution>
    </executions>
</plugin>

This gives your tests more time to run, especially if your app has slow-starting components like database connections or heavy bean initialization.

Even if you can manually access localhost:9990, the wildfly-maven-plugin might be using a too-short timeout for management API calls. Update its configuration:

<plugin>
    <groupId>org.wildfly.plugins</groupId>
    <artifactId>wildfly-maven-plugin</artifactId>
    <version>2.2.0.Final</version>
    <configuration>
        <hostname>localhost</hostname>
        <port>9990</port>
        <!-- Extend management connection timeout to 10 minutes -->
        <timeout>600</timeout>
        <username>admin</username>
        <password>admin</password>
    </configuration>
</plugin>

This ensures the plugin doesn't give up waiting for WildFly to confirm deployment readiness.

WildFly's own internal timeouts might be cutting off deployment or initialization early. Edit your standalone.xml (or domain.xml):

• Adjust the deployment scanner timeout:

  <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
      <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" 
                          scan-interval="5000" deployment-timeout="120"/>
  </subsystem>
  

• If your app uses EJBs or database pools, check their respective timeout settings too. For example, database connection pool timeouts can cause delays that trigger overall deployment timeouts.

Your integration tests might be firing requests before WildFly and your app are fully ready. Add a wait step in your test setup to confirm the app is responsive:

@BeforeClass
public static void waitForAppReady() throws InterruptedException {
    int maxRetries = 30;
    int waitMillis = 1000;
    boolean appReady = false;

    while (maxRetries-- > 0 && !appReady) {
        try {
            URL healthUrl = new URL("http://localhost:8080/your-app/health");
            HttpURLConnection conn = (HttpURLConnection) healthUrl.openConnection();
            appReady = conn.getResponseCode() == 200;
            conn.disconnect();
        } catch (IOException e) {
            Thread.sleep(waitMillis);
        }
    }

    if (!appReady) {
        throw new RuntimeException("App failed to become ready within timeout window");
    }
}

Alternatively, use WildFly's management API to check if your deployment's status is OK before running tests.

Even if you passed Java parameters, insufficient memory can cause slow GC pauses or initialization delays, leading to timeouts. Double-check your WildFly startup args:

-Xms2G -Xmx2G -XX:MetaspaceSize=256M -XX:MaxMetaspaceSize=512M

Adjust values based on your app's resource needs—memory shortages are a sneaky cause of unexpected timeouts.

Start with the plugin timeout settings first—those are the most frequent culprits. If those don't resolve the issue, move on to WildFly's internal config and test readiness checks.

内容的提问来源于stack exchange，提问作者Antoine O