Hello all,
I'm trying to use a database connection pool and decided to go with Poolman
2.0.4 which has been mentioned here in the past.
Unfortunately, I'm getting some spurious SQLExceptions which do not happen
in the non-Poolman case, and was hoping some people may have encountered a
solution to them.
SQLException: Class names may not have _ in them. You supplied {0}.
SQLState: null
VendorError: 0
java.sql.SQLException: Class names may not have _ in them. You supplied {0}.
at
com.codestudio.sql.PoolManPreparedStatement.executeQuery(PoolManPreparedStatement.java:104)
The SQL preparedStatement in question is:
SELECT * FROM broadcast_jobs WHERE job_id=?
This also happens in another case with a similar SQL statement:
SELECT * FROM rules WHERE rule_id=?
In this latter case, sometimes the query succeeds and sometimes it fails.
Does anyone have any idea what may be causing this?
There seems to be no way to NOT use the PoolManPreparedStatement since
that's what the connection returns. The JavaDocs say that it simply wraps
my statement, but this obviously is not the case.
I'm also getting this error on System.out about one trillion times per
application run:
February 27, 2002 7:15:31 PM EST: Driver doesn't support strong
ResultSetMetaData, and PoolMan subsequently failed an attempt to
fabricate a table name in spite of the driver limitations.
Does anyone know how to turn this error report off? It is using up tons of
space in my logs.
Thanks,
Doug
