I think there is a pb the SELECT COUNT(*) request.
Contrary to all other OQL requests, CASTOR doesn't run them in the context of an
explicit database transanction (between a "set autocommit false" and a
"commit/rollback").
This causes pb in a connection pooling context :
if the "set autocommit true" isn't run automaticly by the connection pool
manager (which is the case for JdcbPool for instance),
the SQL COUNT transaction run without commit/rollback on a connection wich
has been previously set by CASTOR in autocommit false mode,
this leads to a transaction CHAINED Exception with Sybase jConnect.
It would be better for CASTOR to send a "set autocommit true" before sending the
SELECT COUNT request to the database server.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
