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 least until there will be a fix > JDK 1.7u3 -- View this message in context: http://tomcat.10.n6.nabble.com/jira-Created-MTOMCAT-125-mvn-tomcat7-run-got-javax-naming-NameNotFoundException-Name-jdbc-is-not-bou-tp4562031p4960028.html Sent from the Tomcat - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
