[ http://issues.apache.org/jira/browse/TRB-5?page=comments#action_12330104 ]
Thomas Vandahl commented on TRB-5: ---------------------------------- This configuration doesn't work for me. The application tries to connect to a default datasource which it didn't do before. The typical error message for something like this in the Torque-log is: --- 2005-09-21 17:40:42,930 [main] WARN org.apache.torque.oid.IDBroker - IDBroker is being used with db 'default', 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. --- This usually means connection problems with a database. Another hint that something strange is going on: I've got two ID-Broker threads running where one should suffice. I use a JNDI DataSource with mysql. Which version of Torque are you using? I have the latest 3.2-rc2. > TorqueSecurityService relies on a datasource named "default" > ------------------------------------------------------------ > > Key: TRB-5 > URL: http://issues.apache.org/jira/browse/TRB-5 > Project: Turbine > Type: Bug > Components: Turbine 2.3 > Environment: Turbine-2.3.2-rc2.-dev > Reporter: Thomas Vandahl > Assignee: Henning Schmiedehausen > > The OM-classes generated during the build process of Turbine need a > hard-coded data source called "default". > The previous version simply used the configured default DataSource as in > torque.database.default=turbine -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
