I just went through the mailing list archive and there was an unresolved thread back in February regarding the IDBroker warning.
"IDBroker is being used with db '<db>', which does not support transactions. IDBroker attempts to use transactions to limit the possibility of duplicate key generation. Without transactions, duplicate key generation is possible if multiple JVMs are used or other means are used to write to the database."
Maybe my scenario will shed a little light on this:
I am using PostgreSQL 7.2.1 in native mode, not IDBroker. I only get the above warning if I attempt to set the transaction isolation level:
torque.dsfactory.<db>.pool.defaultTransactionIsolation=READ_COMMITTED (same result for SERIALIZABLE).
Setting the isolation level also results in Transaction.begin () to fail, which is strange as these are the two isolation levels which PostgreSQL supports.
Why is the IDBroker thread started at all even when using native mode for PK generation?
------
As an aside, and this has nothing to do with the IDBroker issue, I tried to set the following properties as described in the Jakarta Commons dbcp documentation:
torque.dsfactory.<db>.pool.removeAbandoned=true torque.dsfactory.<db>.pool.logAbandoned=true torque.dsfactory.<db>.pool.removeAbandonedTimeout=300
However, these properties are not recognized.
--
Regards,
Tarlika Elisabeth Schmitz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
