Re: Name [comp] is not bound in this Context

well you can test yourself I guess to validate or not this hypothesis but have to admit i didnt see this stack since months to not say years now Romain Manni-Bucau @rmannibucau | Blog | Old Blog

RE: Name [comp] is not bound in this Context

I will try to convince our operations team to do the upgrade, but it's not entirely my call (unfortunately). Cheers, Dmitry -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: May-10-17 1:57 PM To: users@tomee.apache.org Subject: Re: Name [comp] is not boun

Re: Name [comp] is not bound in this Context

Oh 7.0.0, can you give a try on 7.0.3 before we investigate deeper please? Config looks ok. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | Li

RE: Name [comp] is not bound in this Context

Romain, It's TomEE distribution (7.0.0) In the server.xml I can see couple of connectors added: And the Realm for LDAP authentication (added to the localhost Engine): Context.xml is the default one. Dmitry -Original Message- From: Romain Manni-Bucau [mailto:rmanni

Re: Name [comp] is not bound in this Context

Hi Dmitry, do you have some custom config in server.xml or context.xml? Also, do you use tomee distribution or a custom setup based on the war? Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Name [comp] is not bound in this Context

Hi All, I'm getting this error dering deployment of my web app (war): SEVERE - Error merging Java EE JNDI entries in to war /my-app: Exception: null java.lang.NullPointerException at org.apache.catalina.core.NamingContextListener.createSubcontexts(NamingContextListener.java:1291)