You start up a Java process running with the New Relic Java agent, but data fails to report to the APM UI. You see an
Error bootstrapping New Relic agent message in the stack trace in your application logs.
Error bootstrapping New Relic agent can indicate multiple failure modes. The stack trace is also key in diagnosing this issue.
If the Java agent cannot create the temporary
jar files, it will fail to start up and will return the
Error bootstrapping New Relic agent line preceding the stack trace to
System.err. If you are using an app server, this usually appears in your app server's error logs.
Here are common reasons for this failure and the solution.
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.