javax.naming.NameNotFoundException

Name '/resources/foo/bar/l10n/messagebundle_en.properties' does not exist.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3234

  • via rssing.com by Unknown author, 11 months ago
    Name '/resources/foo/bar/l10n/messagebundle_en.properties' does not exist.
  • via rssing.com by Unknown author, 11 months ago
    Name '/resources/foo/bar/l10n/messagebundle_en.properties' does not exist.
  • via rssing.com by Unknown author, 11 months ago
    Name '/resources/foo/bar/l10n/messagebundle_en.properties' does not exist.
  • Stack trace

    • javax.naming.NameNotFoundException: Name '/resources/foo/bar/l10n/messagebundle_en.properties' does not exist. at org.eclipse.gemini.web.tomcat.internal.loading.BundleDirContext.getNamedEntry(BundleDirContext.java:104) at org.eclipse.gemini.web.tomcat.internal.loading.BundleDirContext.doGetAttributes(BundleDirContext.java:169) at org.apache.naming.resources.BaseDirContext.getAttributes(BaseDirContext.java:1102) at org.apache.naming.resources.BaseDirContext.getAttributes(BaseDirContext.java:1055) at org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java:1613) at org.apache.naming.resources.ProxyDirContext.cacheLookup(ProxyDirContext.java:1536) at org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:297) at org.apache.catalina.core.ApplicationContext.getResource(ApplicationContext.java:536) at org.apache.catalina.core.ApplicationContextFacade.getResource(ApplicationContextFacade.java:201) at com.sap.ui5.resource.impl.ServletResourceLocator.findResource(ServletResourceLocator.java:87) at com.sap.ui5.resource.ResourceServlet.findResource(ResourceServlet.java:603) at com.sap.ui5.resource.ResourceServlet.findResource(ResourceServlet.java:622) at com.sap.ui5.resource.ResourceServlet.serveResource(ResourceServlet.java:453) at com.sap.ui5.resource.ResourceServlet.doGet(ResourceServlet.java:191) at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at com.sap.security.auth.service.webcontainer.internal.Authenticator.invoke(Authenticator.java:147) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929) at com.sap.core.tenant.valve.TenantValidationValve.invokeNextValve(TenantValidationValve.java:169) at com.sap.core.tenant.valve.TenantValidationValve.invoke(TenantValidationValve.java:84) at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.