Click the Start a free trial link to start a 30-day SaaS trial of our product and join our community as a trial customer. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
The fact that the agent generated no logs suggests that the agent was never initiated, which suggests that the problem lies in the JVM startup terms.
The documentation for JBoss and Wildfly Startup Settings say:
"Most issues installing the Java Agent on JBoss result from conflicts between startup arguments. That is, settings you add for the Java Agent may be overridden or conflict in other ways with existing arguments. Such issues are not always easy to detect.
The best way to begin troubleshoot such startup issues is to print and inspect the startup arguments that JBoss actually gets when attempting to start."
The suggested remediation is for Linux, but the same applies in a Windows environment.
A good approach is to print out all the JVM arguments from the script and make sure that everything is there.
Also check the logmanager configuration as described on the documentation page, as the wrong configuration can cause startup failures.
Brian Wheeldon, Solution Engineer, NYC