I would say that you need:
torque.database.default=database
But would add that "database" is a bad name to use here. Look at how "bookstore" is used in the example and use your own name (but I would imagine you can think of something more appropriate than "database").
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
Edwin Yearwood wrote:
Hi Henrik,
I've just tried that, and the result was the same.
[DEBUG] TorqueInstance - -Adding a dummy entry for default, mapped onto
oracle
[DEBUG] TorqueInstance - -getConfiguration() =
[EMAIL PROTECTED] [WARN] IDBroker - -IDBroker is being used with db 'DATABASE', 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. [DEBUG] IDBroker - -IDBroker thread was started. There was no DataSourceFactory configured for the connection DATABASE.
Is there a reason why it would complain about this "There was no DataSourceFactory configured for the connection DATABASE" when it has been set.
Thanks.
Edwin Yearwood Developer BTG Reuters
Telephone +44 (0)207 542 5818 Email [EMAIL PROTECTED] Reuters Messaging [EMAIL PROTECTED]
-----Original Message-----
From: Henrik Vendelbo [mailto:[EMAIL PROTECTED] Sent: 04 February 2004 16:55
To: Apache Torque Users List
Subject: Re: IDBroker warning
have you tried
torque.database.default=oracle ?
----- Original Message ----- From: "Edwin Yearwood" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 04, 2004 4:25 PM
Subject: FW: IDBroker warning
Can anyone help with the following problem we're experiencing.
Thanks.
Edwin Yearwood Developer BTG Reuters
Telephone +44 (0)207 542 5818 Email [EMAIL PROTECTED] Reuters Messaging [EMAIL PROTECTED]
-----Original Message-----
From: Edwin Yearwood Sent: 03 February 2004 11:56
To: Apache Torque Users List
Subject: RE: IDBroker warning
Hi Scott,
I've trawled the archives to no avail, there doesn't seem to be any specific resolution to this issue, Stephen Haberman's response to a similar problem "nDataSourceFactory error about Idbroker when Id broker not set" only suggests that the torque configuration is incorrect. I've tried changing the config around but nothing works. I also get the following error message from torque "There was no DataSourceFactory configured for the connection DATABASE" similar to that in the archive message highlighted above.
I'm currently using Oracle 8i with following torque config. This config has worked with the bookstore example @ Torque Home the only difference is with the database connection properties.
# ------------------------------------------------------------------- # $Id: Torque.properties,v 1.11 2003/08/19 19:09:44 mpoeschl Exp $ # # This is the configuration file for Torque. # # Note that strings containing "," (comma) characters must backslash # escape the comma (i.e. '\,') # # -------------------------------------------------------------------
torque.applicationRoot = .
# ------------------------------------------------------------------- # # L O G G I N G # # ------------------------------------------------------------------- # We use Log4J for all Torque logging and we embed the log4j # properties within our application configuration. # -------------------------------------------------------------------
# This first category is required and the category # must be named 'default'. This is used for all logging # where an explicit category is not specified.
log4j.category.org.apache.torque = ALL, org.apache.torque log4j.appender.org.apache.torque = org.apache.log4j.FileAppender log4j.appender.org.apache.torque.file = ${torque.applicationRoot}/logs/torque.log log4j.appender.org.apache.torque.layout = org.apache.log4j.PatternLayout log4j.appender.org.apache.torque.layout.conversionPattern = %d [%t] %-5p %c - %m%n log4j.appender.org.apache.torque.append = false
# ------------------------------------------------------------------- # # D E F A U L T S # # ------------------------------------------------------------------- # # These values kick in, if you don't explicitly override them in your # various database settings. At the moment they're only used if you # configure the TorqueDataSourceFactory of the Jdbc2PoolDataSourceFactory # as your data source provider. It does not work with JNDI. # # The example is shown for TorqueDataSource. # # -------------------------------------------------------------------
# If > 0, then a monitoring thread is started for every pool to # display the number of created, available and checked out connections # The interval is in seconds. torque.defaults.pool.logInterval = 0
# Time to wait for a connection to the databas in Seconds. torque.defaults.pool.connectionWaitTimeout = 10
# Maximum number of connections cached in a database definition. Note # that, if you have multiple database definitions which access the # same database URL, they don't share the connections but you have # multiple pools and each has this maximum number. So if you have a # connection licensed database engine, you must multiply this number by # the number of times you use a specific database URL. torque.defaults.pool.defaultMaxConnections = 80
# Lifetime of a connection in the pool. Defaults to one hour torque.defaults.pool.maxExpiryTime = 3600
# Sets the driver for the data sources. torque.defaults.connection.driver = org.gjt.mm.mysql.Driver
# Sets the URL for the datasources torque.defaults.connection.url = jdbc:mysql://localhost:3306/torque
# Sets login and password for the data sources. torque.defaults.connection.user = user torque.defaults.connection.password = password
# ------------------------------------------------------------------- # # T O R Q U E P R O P E R T I E S # # ------------------------------------------------------------------- # These are your database settings. Look in the # org.apache.torque.pool.* packages for more information. # # The parameters to connect to the default database. You MUST # configure these properly. # -------------------------------------------------------------------
#torque.database.default=bookstore #torque.database.bookstore.adapter=mysql
## Using torque's old pool ## this implementation is deprecated and has some known bugs!!!! ## you should use commons-dbcp #torque.dsfactory.bookstore.factory=org.apache.torque.dsfactory.TorqueDa taSourceFactory #torque.dsfactory.bookstore.pool.defaultMaxConnections=10 #torque.dsfactory.bookstore.pool.maxExpiryTime=3600 #torque.dsfactory.bookstore.pool.connectionWaitTimeout=10 #torque.dsfactory.bookstore.connection.driver = org.gjt.mm.mysql.Driver #torque.dsfactory.bookstore.connection.url = jdbc:mysql://localhost:3306/torque #torque.dsfactory.bookstore.connection.user = user #torque.dsfactory.bookstore.connection.password = password
## Using commons-dbcp torque.database.database.adapter=oracle torque.dsfactory.database.factory=org.apache.torque.dsfactory.SharedPool DataSourceFactory #torque.dsfactory.database.factory=org.apache.torque.dsfactory.Jdbc2Pool DataSourceFactory #torque.dsfactory.bookstore.factory=org.apache.torque.dsfactory.PerUserP oolDataSourceFactory torque.dsfactory.database.pool.defaultMaxActive=10 torque.dsfactory.database.pool.testOnBorrow=true torque.dsfactory.database.pool.validationQuery=SELECT 1 torque.dsfactory.database.connection.driver = oracle.jdbc.driver.OracleDriver torque.dsfactory.database.connection.url = jdbc:oracle:thin:@<host>:<port>:Database torque.dsfactory.database.connection.user = <username> torque.dsfactory.database.connection.password = <password>
## Using jndi #torque.dsfactory.bookstore.factory=org.apache.torque.dsfactory.JndiData SourceFactory #torque.dsfactory.bookstore.jndi.path=jdbc/bookstore #torque.dsfactory.bookstore.jndi.java.naming.factory.initial = org.apache.naming.java.javaURLContextFactory #torque.dsfactory.bookstore.jndi.java.naming.factory.url.pkgs = org.apache.naming
#torque.dsfactory.bookstore.datasource.classname=org.apache.torque.pool. TorqueClassicDataSource #torque.dsfactory.bookstore.datasource.dataSourceName=jdbc/DBbookstore #torque.dsfactory.bookstore.datasource.jndiEnvironment.java.naming.facto ry.initial = org.apache.naming.java.javaURLContextFactory #torque.dsfactory.bookstore.datasource.jndiEnvironment.java.naming.facto ry.url.pkgs = org.apache.naming #torque.dsfactory.bookstore.datasource.defaultMaxConnections=10
## ConnectionPoolDataSource #torque.dsfactory.bookstore.factory=org.apache.torque.dsfactory.JndiData SourceFactory #torque.dsfactory.bookstore.jndi.path=jdbc/DBbookstore #torque.dsfactory.bookstore.jndi.java.naming.factory.initial = org.apache.naming.java.javaURLContextFactory #torque.dsfactory.bookstore.jndi.java.naming.factory.url.pkgs = org.apache.naming #torque.dsfactory.bookstore.datasource.classname=org.apache.commons.dbcp .cpdsadapter.DriverAdapterCPDS #torque.dsfactory.bookstore.datasource.driver = org.gjt.mm.mysql.Driver #torque.dsfactory.bookstore.datasource.url = jdbc:mysql://localhost:3306/torque #torque.dsfactory.bookstore.datasource.user = user #torque.dsfactory.bookstore.datasource.password = password
# Determines if the quantity column of the IDBroker's id_table should # be increased automatically if requests for ids reaches a high # volume.
torque.idbroker.cleverquantity=true
# Determines whether the managers cache instances of the business objects. # And also whether the MethodResultCache will really cache results.
torque.manager.useCache = true
# tutorial: log4j.rootCategory = DEBUG, default log4j.appender.default = org.apache.log4j.FileAppender log4j.appender.default.file = ./torque.log log4j.appender.default.layout = org.apache.log4j.SimpleLayout
torque.database.default=Database torque.database.database.driver = oracle.jdbc.driver.OracleDriver torque.database.database.url = jdbc:oracle:thin:<host>:<port>:Database torque.database.database.username = <username> torque.database.database.password = <password>
Thanks for any help you can provide.
Edwin Yearwood Developer BTG Reuters
Telephone +44 (0)208 542 5818 Email [EMAIL PROTECTED] Reuters Messaging [EMAIL PROTECTED]
-----Original Message-----
From: Scott Eade [mailto:[EMAIL PROTECTED] Sent: 02 February 2004 21:45
To: Apache Torque Users List
Subject: Re: IDBroker warning
Edwin Yearwood wrote:
Has any one seen the following message before?, and if you have can you
help me out with the solution "[WARN] IDBroker - -IDBroker is being used with db 'DATABASE', which does not support transactions...".What RDBMS are you using? This message will typically appear when the RDBMS in use does not support transactions (e.g. MySQL), though if you search the archives you may find queries and answers concerning occurrences of this message when transactions are in fact supported.
Scott
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
