It seems to me a problem related to a naming bug in JDK 1.7.x
I had similar problems using Glassfish when I upgraded from 3.1.1 to 3.1.2
and on that time the JDK 1.7.x was recommended... I did it and my stable
enterprise application stopped working.
I would recommend to stay with JDK 1.6.x at
Java 7 u4 is available for some time now.
Did you try it ?
Le 8 mai 2012 à 12:03, Roberto Cisternino roberto.cistern...@gmail.com a
écrit :
It seems to me a problem related to a naming bug in JDK 1.7.x
I had similar problems using Glassfish when I upgraded from 3.1.1 to 3.1.2
and on that
Unfortunately do not seems to contain any fix related to that issue.
I hope to find the time to get my logs and extract full details to open an
issue asap.
Thanks
On Tue, May 8, 2012 at 2:28 PM, Henri Gomez [via Tomcat]
ml-node+s10n4960281...@n6.nabble.com wrote:
Java 7 u4 is available for
mvn tomcat7:run got javax.naming.NameNotFoundException: Name jdbc is not bound
in this Context
Key: MTOMCAT-125
URL:
