-
Notifications
You must be signed in to change notification settings - Fork 324
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.
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
Application deployment fails when setting trace_methods #474
Comments
Elastic APM agent version is 1.3.0. |
Should be fixed with #432. |
@TeroPihlaja Also, please be very aware to what you define to be traced using this configuration. Such a wide wildcard would probably be OK of debugging, but not so for production. It's advisable to be (much) more specific in what you choose to instrument. The instrumentation overhead may still remain negligible, but sending and storing spans for ALL methods may be way too much. |
Hello, Yes, I believe that option needs tuning for production. Looks like same/similar error with the snapshot:
|
We believe this is a problem with the byte code EclipseLink generates for the generated |
This project is using |
@TeroPihlaja please test this one: |
Seems to work! |
That's great to hear! You can continue using this snapshot for evaluation and the next release will include the fix. |
Describe the bug
Application deployment fails when setting trace_methods to "all"
trace_methods=com.vilant.*#*
Payara 5.183
Oracle java version "1.8.0_172"
Debug logs
Attach your debug logs.
See the documentation
about how to enable debug logging.
Click to expand
The text was updated successfully, but these errors were encountered: