Skip to content

add tip on wrong jar file usage #661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 12, 2019
Merged

add tip on wrong jar file usage #661

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-<version>.jar` and
further information about how to download this file can be found <<setup-javaagent, in the manual setup instructions.>>