Before you install New Relic's Java agent, make sure your WildFly version is supported. Depending on which WildFly version your application uses, additional configuration steps may be required.
If your supported WildFly version is earlier than v11, follow standard Java installation procedures. You do not need to do any additional configuration.
If you use WildFly version 11 or higher, New Relic's Java agent requires additional configuration after you install it.
standaloneconfiguration file appropriate for your operating system and add the -javaagent property to
JAVA_OPTS. For example, if you use Linux, edit the
Make sure the agent
jaris visible to all JBoss modules by adding
com.newrelicto the JBoss modules system packages using either of these options in the
Recommended: Option 1 (same as adding
Option 2:if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; thenJBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,com.newrelic"fi
Restart your application server.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.