From 8f489b2e8736ffef4c3652212827e6a81267a1db Mon Sep 17 00:00:00 2001 From: Peter Dyson Date: Wed, 12 Jun 2019 14:52:19 +1000 Subject: [PATCH] add tip on wrong jar file usage --- docs/troubleshooting.asciidoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/troubleshooting.asciidoc b/docs/troubleshooting.asciidoc index c46fa0de87..d78b67cac7 100644 --- a/docs/troubleshooting.asciidoc +++ b/docs/troubleshooting.asciidoc @@ -160,3 +160,14 @@ Consider updating to a newer version of that library. That mostly concerns JDBC drivers. Updating them to a more recent version should resolve the problem. + +[float] +[[trouble-shooting-incorrect-manual-jar-file]] +==== Failed to find Premain-Class manifest attribute ==== + +If you are using a manual setup with a `-javaagent` flag against an application server and are seeing the +`Failed to find Premain-Class manifest attribute` error and a failure to start, then you might be pointing +at the incorrect jar file. + +The correct jar file to be pointing at should be in the form of `elastic-apm-agent-.jar` and +further information about how to download this file can be found <>