Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`javax.naming.NameNotFoundException` thrown at application startup
See original GitHub issueWhen creating a cache via Cache2kBuilder, the Cache2kCoreProviderImpl tries to register org.cache2k.CacheManager.defaultName through JNDI and it fails with javax.naming.NameNotFoundException: Name [org.cache2k.CacheManager.defaultName] is not bound in this Context. Unable to find [org.cache2k.CacheManager.defaultName].
The application is running within Tomcat. The application starts up without issues, but I would like to avoid having a stack trace at start time. Is there a way to disable this behaviour?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Verison 1.2.4.Final is released now with this fix.
You could simply set the JNDI property
org.cache2k.CacheManager.defaultNametodefault.I will do an update, so this gets silently ignored. Maybe I drop JNDI in the futures, since I think not many are using this.