Known Issues - Java Controller Installations
How To’s
- Create a new vFunction Agent Instance
- Disable Tracking of Files
- Disable Tracking of Spring Beans and Class Loader Resources
- Reject Java Classes from being sent to the vFunction Server for Analysis
- Switch Database Tracking Mechanism
- Use Environment Variables for vFunction Installation parameters
- Use an Existing OpenTelemetry Agent for Database Tracking
Known Issues
- After upgrading to a Controllerless Dynamic Agent, the Agent does not show Status: Up in the vFunction Server UI
- Agent’s Temp Directory contains a large number of files and takes up a large amount of disk space
- Application logging throws SaxParseException Premature End of File error
- Application logging throws vfrtshadow ClassCastException
- Application logging throws vfrtshadow ConnectionWrapper cannot be cast to DB Connection error
- Application logging throws ‘Wrong Type At Constant Pool Index’ error
- Capture Database Tracking on Java Applications with OSGI Bundles
- Configuring WebLogic with Node Manager
- Crash when using IBM Java SDK 8
- Error ‘A timer for thread already exists in the list’ when two agentpath parameters added to JVM
- Error ‘Invalid Byte Tag in Constant Pool’ when Java Agent added to Tomcat Application Server
- Error ‘Parsing error. Unexpected end of data’ when vFunction Agent added to Jboss or Wildfly Application Server
- Error ‘Unrecognized Options –add-opens’ when vFunction Agent added to a Java Springboot Application running Java 17
- Error, ‘UnsatisfiedLinkError’ on DynatraceOutgoingHttpCloudEvents after adding vFunction Runtime Agent to a Java Application with the Dynatrace OneAgent also added
- Java Application hangs while running Batch Jobs
- JBoss Logging Manager exception after adding vFunction Agent
- ‘NoClassDefFoundError: /io/smallrye/common/net/HostName’ on containerized Wildfly after adding vFunction Agent
- ‘NoClassDefFoundError: /org/wildfly/common/net/HostName’ on containerized Wildfly after adding vFunction Agent
- ‘Permission Denied’ error when adding vFunction Agent to Tomcat Application Server
- See MongoDB Collections as Database Tables in the vFunction Server UI
- Standard Output includes VFAgent Configuration Details when saving Standard Output
- Upgrading a vFunction Controller from a version 4.0 to a version above 4.0 creates a new instance
- Vfagent.log.dbtracking throws warning that SQL Cache Exceeded
- vFunction Flags not recognized in Spring Boot application
- WebSphere AccessControlException in native_stderr.log
- With a Java 6 or 7 Application and HTTPS configured for the vFunction Server, the Agent throws a handshake_failure SSL Exception