Well, I don't like a context name of "[]". It should be something like "/" or "/myapp". Maybe you deployed an app with context name = ""?
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Joe Harry wrote:I can check that, but what has that got to do with the exception that I get here with respect to the MySQL driver? Any ideas?
When I have an error coming from a bad app, the first thing I do is find out what's wrong with the app. Fixing that often fixes the other errors.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
And ignore what it says about server.xml. Someone needs to update that.
Typical usage:
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
You can do that. Or you can create a file with a Tomcat Context in it and place it in TOMCAT_HOME/conf/Catalina/localhost. Since there can be multiple contexts in there, obviously they can't all be named "context.xm", but any file with an ".xml" suffix will be scanned by Tomcat and the name of the file doesn't have to match the context. Although it makes life easier if they do match.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.