-
Notifications
You must be signed in to change notification settings - Fork 508
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 fails to start with StackOverflowError #209
Comments
I'm experiencing the same, starting with version Versions:
I'm sticking with |
@gmacster @steinwelberg are you able to upload a minimal example repository that replicates the bug? If so, I can take a look at trying to fix it. |
@rupert-madden-abbott Minimal example uploaded at https://github.com/gmacster/jasypt-spring-boot-stackoverflowerror It appears to only be an issue when The example has the following versions:
|
I am facing this issue as well with
|
Try excluding all vcap.* properties from being introspected. Check the readme for details on how to do that |
I am confused on which exclusion property to use. Is it one of the below?
As mentioned in my previous post, I assign the vcap services value to jasypt.encyptor.password. Isn't jasypt.encryptor already included in the exclusion list by DefaultPropertyFilter? Below is the error that I receive:
Thanks in advance for your response. |
you can use: jasypt.encryptor.property.filter.exclude-names=vcap.services.pcf-credhub-service.credentials.jasypt-password
// or
jasypt.encryptor.property.filter.exclude-names=vcap.services.pcf-credhub-service.credentials.*
// or, if you know the property source name and for instance is called "vcap-services"
jasypt.encryptor.property.filter.exclude-sources=vcap-services |
I tried the above options already but it didn't help. I received the same StackOverflowError and the server failed to start. |
can you provide an example project where this happens? what option above did you actually used? Can I have a full stack trace? In the original stack trace (not from @gsakthinarayanan ) I see that |
@gsakthinarayanan @gmacster @steinwelberg can you try this? jasypt.encryptor.property.filter.exclude-names=jasypt.encryptor.password |
I tried the above recommendation but still the same error. I created a sample repository that recreates the below issue. With spring boot jasypt starter 3.0.3 (below issues do not occur with version 2.1.1):
Thanks for your response. |
Any update on this? I am having the same exact issues described above.
Repeats about 20 times before failing with StackOverflow |
I found the issue. Haven’t had the chance to fix it yet |
What is the issue? Also, is there a version where the issue isn't present? I've seen some say version 3.0.0 is fine to use. Should I revert back to version 2.1.2? |
It has to do with the way the beans are lazily initialized. They look for a property but the property kicks in the encryption stuff which triggers to load the filters, and so on until it blows up. |
Any update on this issue? I'm getting the same error:
|
Same issue here when having the password in a PCF CredHub. Any updates? Thanks! |
I have upgraded and stackOverflow was fixed. |
having same issue when defining |
Same issue. application.properties (really yaml) jasypt 3.0.1 release notes: |
Hello, Same issue here with spring-boot 2.4.5 -> 2.5.4 and jasypt-spring-boot-starter 3.0.3. I have a configuration like : The following log and stacktrace happen when the file is not provided :
|
should go out next release |
When I integrate Jasypt version
3.0.2
into my application I receive a StackOverflowError and my application won't start.Versions:
jasypt-spring-boot-starter
version3.0.2
spring-boot
version2.2.6.RELEASE
spring
version5.2.5.RELEASE
I have followed the steps to integrate Jasypt into my application and when I start the application I see the following stacktrace:
Stacktrace
Before the stacktrace I see the following log message 142 times:
And before that I see that my property files get wrapped into the
EncryptableMapPropertySourceWrapper
object:The text was updated successfully, but these errors were encountered: