-
-
Notifications
You must be signed in to change notification settings - Fork 443
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
Failed to bind properties under 'sentry.parsed-dsn' to io.sentry.Dsn #3825
Comments
Thanks for opening this issue @detomarco ! Are you sure this worked before? However setting Could share a few more details about your environment / sentry setup? |
I have the same problem. When I use 7.16.0, I get the same error. Hovever when I use 7.15.0, I don't get any error. I use springboot v3.3 and there's application.yaml with param |
I've done some testing and so far I'm unable to reproduce the exact problem ( Can you please share more details like integrations used, config settings etc.? |
I managed to reproduce this, using Spring Boot 3.3.5 and Sentry 7.16.0. For some reason for me this does not happen when using embedded tomcat but does happen when deploying traditional WAR to Tomcat. I have this in my application.properties
Stacktrace:
|
Thanks for providing more info @micopiira, we'll take another look |
Hi @micopiira @detomarco, It seems that, in contrast to the embedded Tomcat, the standalone Tomcat has Renaming the method to |
@detomarco @micopiira @evmetatron we've released https://github.com/getsentry/sentry-java/releases/tag/7.17.0 which includes a fix for this problem. If you decide to give it a try - feedback would be great. |
@adinauer Thank you, can confirm that the version 7.17.0 works as expected. |
Thank you for the feedback! |
Integration
sentry
Java Version
22
Version
7.16.0
Steps to Reproduce
Use version 7.16 and set
SENTRY_DSN=""
(empty string)Expected Result
Application starts and sentry is disabled
Actual Result
from Sentry v7.16.0 I get this error
I think it's related to this PR #3796
The text was updated successfully, but these errors were encountered: