As you note in a later message, if you use the XADataSourceLoader
it assumes a transaction environment - that is, any changes not executed
with the scope of a transaction are rolled back. We have not provided an
example for JDBCDataSourceLoader because transaction handling is a major
feature of EJB and we don't see why you'd want to defeat it. But it is
there, if you're really desperate. Do you have a really compelling reason
to manage transactions yourself without using the EJB/JTA facilities
provided for you?
Aaron
On Tue, 28 Nov 2000, Wes Mckean wrote:
> I have a connection pool setup using the iNet driver. I can see that when
> the connection pool is started, a BEGIN TRANSACTION is issued on the
> connection in MS SQL Server. After every SQL statement executed (viewed
> using trace), I see the SQL statement IF @@TRANCOUNT > 1 ROLLBACK TRAN
> BEGIN TRAN
>
> This is causing any updates I do to be rolled back. My test entity bean is
> setup to not use transactions. I believe this is happening because the data
> pool sets auto commit to false when it creates the connection. This doesn't
> make sense to me, since the connection will remain around in the pool for a
> long time, and it is unlikely that the bean will or anything else for that
> matter will do a RANDOM COMMIT TRANS to cause everything done on that
> connection to flush. So, any updates, inserts, or deletes done on this
> connection will not be committed, ever.
>
> Is this an error on the part of the TDS driver? Or is it an error of
> Minerva? Why does Minerva need to set auto commit off, if transaction
> management will handle this?
>
> Wes
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
