`javax.naming.NameNotFoundException` thrown at application startup

[luciano-fiandesio]

When 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?

[cruftex]

The purpose of the JNDI property is to set a different cache manager name, in case you run multiple applications with cache2k within one tomcat instance.

When nothing is set, this should be ignored. Seems like you found a bug. Sorry for that. Will correct that ASAP.

[cruftex]

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?

You could simply set the JNDI property org.cache2k.CacheManager.defaultName to default.

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.

[luciano-fiandesio]

Ok, thanks. Yeah, I think you can simply catch javax.naming.NameNotFoundException in JndiDefaultNameProvider.registerCache2kExtension and ignore

[cruftex]

Trying to release but unfortunately, I am getting timeouts from Sonatype for the Maven central upload at the moment.

[cruftex]

Verison 1.2.4.Final is released now with this fix.

[luciano-fiandesio]

Verison 1.2.4.Final is released now with this fix.

Excellent, thanks for the crazy fast response