On Nov 20, 2008, at 10:30 , Christopher Schultz wrote:
Len is absolutely right: the exception is being thrown by MySQL, so
it's
their error message. Was there a "root cause" printed with this stack
trace? That certainly would have helped.
I checked the source for Connector/J 5.1.6 and that exception is only
thrown in a single place: SQLError.java:1070. When that exception is
created, the underlying exception is, in fact, passed up to
java.lang.Throwable via the initCause method. So, there should have
been
a "caused by" line in that stack trace.
I hadn't thought about the MSQL connector consuming the exception and
then throwing one of its own. Now this make perfect sense.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
