Youngho Cho wrote:
It looks like the torque initialize process has a problem for checking Tranasction Support or Not. During initialize process, the IDBroker call the TorqueInstance for checking the Connection support transaction. Because the TorqueInstance doesn't initialize yet, it always set false even the connection support transaction.
I use Torque 3.2-dev with MySQL InnoDB tables and it works fine. The warning below appears if Torque cannot connect to the database for whatever reason. Probably because it is not initialized correctly as the error message suggests.
2005-06-23 23:31:15,078 [main] ERROR org.apache.torque.oid.IDBroker - org.apache.torque.TorqueException: Torque is not initialized. 2005-06-23 23:31:15,078 [main] WARN org.apache.torque.oid.IDBroker - IDBroker is being used with db 'easydesk', 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.
Could you please post your Torque.properties? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
