Manu, I've had a experience that has some similarity to your problem with the 'classic' configuration. On the jdbc URL I added the following SelectMethod=cursor. I believe the switch controls transaction behavior and how data is transferred from SQL server to client. HOWEVER, my environment is very different from yours, I'm running against SQL Server 2000 sp1 using m$ supplied JDBC driver. I see you are using a different driver (and server), see if there is a similar switch to SelectMethod.
Steve example jdbc url: jdbc:microsoft:sqlserver://localhost:1433;databasename=mydb;SelectMethod=cur sor > -----Original Message----- > From: Emmanuel JEGOU [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 27, 2002 7:49 AM > To: [EMAIL PROTECTED] > Subject: Connection to MSSQL Server : Transaction problems... > > > Hello, > > I am trying to use Torque to connect to a MS SQL Server 7 database. > > When I use a 'dsn' configurationin the Torque.properties, there is no > problem. But when I try using a 'classic' configuration, I have a > transaction problem. > > No transaction is supported is the message returned by Torque. > > I use it with om Objects. I have no problem with a postgres database, just > only with MS SQL Server... > > > If someone could help me... > > Thanks, > > Manu. > > --- > Using Torque 3.0rc1 > > ErrorMessage returned with 'classic' configuration : > >============= > - IDBroker is being used with db 'ADMIN_CLIDON', 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. > > java.lang.NullPointerException: Connection object was null. This could be > due to a misconfiguration of the DataSourceFactory. Check the logs and > Torque.properties to better determine the cause. > > <============= > > > Torque.properties with 'dsn' configuration : > >============= > torque.database.ADMIN_CLIDON.adapter=mssql > > ## Using torque's old pool > > torque.dsfactory.ADMIN_CLIDON.factory=org.apache.torque.dsfactory. > TorqueData > SourceFactory > > torque.dsfactory.ADMIN_CLIDON.pool.defaultMaxConnections=10 > > torque.dsfactory.ADMIN_CLIDON.pool.maxExpiryTime=3600 > > torque.dsfactory.ADMIN_CLIDON.pool.connectionWaitTimeout=10 > > torque.dsfactory.ADMIN_CLIDON.connection.driver = > sun.jdbc.odbc.JdbcOdbcDriver > > torque.dsfactory.ADMIN_CLIDON.connection.url = > jdbc:odbc:dsn-SQLADMIN-ADMIN_CLIDON > > torque.dsfactory.ADMIN_CLIDON.connection.user = > > torque.dsfactory.ADMIN_CLIDON.connection.password = > > <============= > > Torque.properties with 'classic' configuration : > >============= > torque.database.ADMIN_CLIDON.adapter=mssql > > ## Using torque's old pool > > torque.dsfactory.ADMIN_CLIDON.factory=org.apache.torque.dsfactory. > TorqueData > SourceFactory > > torque.dsfactory.ADMIN_CLIDON.pool.defaultMaxConnections=10 > > torque.dsfactory.ADMIN_CLIDON.pool.maxExpiryTime=3600 > > torque.dsfactory.ADMIN_CLIDON.pool.connectionWaitTimeout=10 > > torque.dsfactory.ADMIN_CLIDON.connection.driver = > net.sourceforge.jtds.jdbc.Driver > > torque.dsfactory.ADMIN_CLIDON.connection.url = > jdbc:jtds:sqlserver://sqladmin:1433/ADMIN_CLIDON > > torque.dsfactory.ADMIN_CLIDON.connection.user = > > torque.dsfactory.ADMIN_CLIDON.connection.password = > > <============= > > > > > __________________________________________________ > Modem offert : 150,92 euros rembours�s sur le Pack eXtense de Wanadoo ! > Haut d�bit � partir de 30 euros/mois : http://www.ifrance.com/_reloc/w > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
