This guide covers common issues when using WildFly Testing Tools. For module-specific troubleshooting, see:
-
Extension Troubleshooting - Server startup, deployment, and lifecycle issues
1. Debug Logging
Enabling debug logging is often the first step in troubleshooting issues.
1.1. JBoss Log Manager
If using the JBoss Log Manager, add to src/test/resources/logging.properties:
loggers=org.wildfly.testing,org.jboss.as.controller.client
logger.level=INFO
logger.handlers=FILE,CONSOLE
# Enable framework debug logging
logger.org.wildfly.testing.level=${test.log.level:DEBUG}
# Enable WildFly client logging
logger.org.jboss.as.controller.client.level=${test.log.level:DEBUG}
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.formatter=COLOR-PATTERN
handler.CONSOLE.properties=autoFlush,target
handler.CONSOLE.autoFlush=true
handler.CONSOLE.target=SYSTEM_OUT
handler.FILE=org.jboss.logmanager.handlers.FileHandler
handler.FILE.formatter=PATTERN
handler.FILE.properties=autoFlush,append,fileName
handler.FILE.constructorProperties=fileName,append
handler.FILE.autoFlush=true
handler.FILE.append=true
handler.FILE.fileName=${client.log.dir}/tck-client.log
formatter.COLOR-PATTERN=org.jboss.logmanager.formatters.ColorPatternFormatter
formatter.COLOR-PATTERN.properties=pattern
formatter.COLOR-PATTERN.pattern=[client] %d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%e%n
formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.PATTERN.properties=pattern
formatter.PATTERN.pattern=%d{yyyy-MM-dd'T'HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%e%n
1.2. Other Logging Frameworks
For Log4j2, Logback, or Java Util Logging, configure the org.wildfly.testing and org.jboss.as.controller.client loggers at DEBUG level according to your logging framework’s configuration format.
2. Remote Debugging
Debug WildFly during tests:
mvn test -Dwildfly.debug
Then attach your IDE’s debugger to port 8787.
mvn test -Dwildfly.debug -Dwildfly.debug.port=5005
Then attach your IDE’s debugger to port 5005.
The wildfly.debug properties only work for standalone mode tests.
|
3. Module-Specific Issues
For issues specific to each module, consult the module documentation:
-
API Documentation - @RequiresModule, @AnyOf, @JBossHome issues
-
Extension Troubleshooting - Comprehensive troubleshooting for server lifecycle, deployments, and domain mode
-
Tools Documentation - DeploymentDescriptors and ModuleBuilder usage
4. Getting Help
If you’re still experiencing problems:
-
Check the GitHub Issues for known problems
-
Review the JavaDoc API documentation
-
Ask for help on the WildFly Zulip Chat
-
Report bugs at GitHub