...
[15:13:30 CDT(-0500)] <EricDalquist> thanks drewwills
[15:19:45 CDT(-0500)] <drewwills> does uP use c3p0?
[15:19:49 CDT(-0500)] <EricDalquist> no
[15:19:56 CDT(-0500)] <drewwills> didn't think so
[15:19:57 CDT(-0500)] <EricDalquist> we switched to tomcat 7's JDBC pool
[15:20:06 CDT(-0500)] <EricDalquist> it is fairly new
[15:20:09 CDT(-0500)] <drewwills> yeah, that rings a bell
[15:20:12 CDT(-0500)] <EricDalquist> but an in spirit DBCP replacement
[15:20:22 CDT(-0500)] <EricDalquist> that uses the JDK6+ concurrency APIs
[15:20:25 CDT(-0500)] <drewwills> i'm seeing this: https://gist.github.com/drewwills/5257635
[15:20:27 CDT(-0500)] <EricDalquist> and has MUCH nicer config
[15:20:33 CDT(-0500)] <drewwills> with jtds 1.3 and jdk7
[15:20:41 CDT(-0500)] <EricDalquist> jtds is jsut evil 
[15:21:00 CDT(-0500)] <drewwills> found this page, which describes a really similar error: https://github.com/swaldman/c3p0/issues/5
[15:21:09 CDT(-0500)] <drewwills> but it says the issue is older c3p0
[15:21:59 CDT(-0500)] <EricDalquist> http://sourceforge.net/p/jtds/discussion/104389/thread/f709d990
[15:22:04 CDT(-0500)] <EricDalquist> it is just that driver
[15:22:15 CDT(-0500)] <EricDalquist> honestly we need someone who uses mssql
[15:22:20 CDT(-0500)] <EricDalquist> to update the manual
[15:22:25 CDT(-0500)] <EricDalquist> with how to use the MS JDBC driver
[15:22:36 CDT(-0500)] <EricDalquist> jtds is apparently not keeping up with the JDBC APIs
[15:23:16 CDT(-0500)] <drewwills> no kidding
[15:23:37 CDT(-0500)] <drewwills> reached the bottom of the page... they seemed to have it well-diagnosed