With a JBoss Application Server, a Java App does not display Database Tracking tables using any vFunction Database Tracking workflow
Overview of the Issue
This issue occurs in the following circumstances:
- A vFunction organization runs their Java Application on a JBoss or Wildfly Application Server
- The organization hooks their Java App with the vFunction Java Runtime Agent
- Unexpectedly, the vFunction Server UI does not display any Database Tables in the Resources Report after testing is completed
- The vFunction organization switches the Database Tracking mechanism to disable_jdbc: true in the installation.yaml, runs the vFunction upgrade script, and restarts the JVM
- Unexpectedly, the vFunction Server UI does not display any Database Tables in the Resources Report after testing is completed
- The vFunction organization adds the OpenTelemetry Java Agent to the JVM Startup Parameters and switches the Database Tracking mechanism to use the OpenTelemetry Java Agent (see steps 6-10 in the linked article)
- Unexpectedly, the vFunction Server UI does not display any Database Tables in the Resources Report after testing is completed
Steps to Resolve the Issue
This issue has been resolved in vFunction Java Agent version 5.0 and later. Upgrade the vFunction Java Agent to this a version in which this issue has been resolved.
In vFunction Java Agent 5.0 and later, the following System Packages are added automatically to the JBoss Modules:
-Djboss.modules.system.pkgs=com.vfunction,vfrtshadow,io.opentelemetry.javaagent,io.opentelemetry.javaagent.bootstrap