From torque-user-return-6794-apmail-db-torque-user-archive=db.apache.org@db.apache.org Thu Feb 16 18:46:54 2006 Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 5813 invoked from network); 16 Feb 2006 18:46:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Feb 2006 18:46:54 -0000 Received: (qmail 18268 invoked by uid 500); 16 Feb 2006 18:46:52 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 18246 invoked by uid 500); 16 Feb 2006 18:46:52 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 18235 invoked by uid 99); 16 Feb 2006 18:46:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2006 10:46:52 -0800 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of Greg.Monroe@dukece.com designates 65.112.55.73 as permitted sender) Received: from [65.112.55.73] (HELO mail.dukece.com) (65.112.55.73) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Feb 2006 10:46:51 -0800 Received: from dukece-mail3.dukece.com ([192.168.1.222]) by mail.dukece.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 16 Feb 2006 13:46:39 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: What are possible causes of: IDBroker ... does not support transactions. Date: Thu, 16 Feb 2006 13:46:28 -0500 Message-ID: <8F5843B903F59D4C8C6806BB49A391190629A7@dukece-mail3.dukece.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What are possible causes of: IDBroker ... does not support transactions. Thread-Index: AcYzJPLh7TxkA2JHR6OsFN2pCB3awAAAcc2g From: "Greg Monroe" To: "Apache Torque Users List" X-OriginalArrivalTime: 16 Feb 2006 18:46:39.0781 (UTC) FILETIME=[5285BD50:01C63329] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hmm, at this point, I'd try doing a simple jsp page to manually open the DB and do a simple query with=20 straight JDBC calls using the DB URL and other info=20 in the Torque properties. Something like: <%@ page import=3D"java.sql.*" %> <% Driver driver =3D (Driver)Class. forName().newInstance(); Connection conn =3D=20 DriverManager.getConnection(,,"); ResultSet rs =3D stmt.executeQuery(); if (rs !=3D null) { %> Found <%=3Drs.size()%> results. <% } else %> ResultSet was null! <% } %> If this page works from the same WebApp, then you=20 know it's not a connection, class path, driver issue and can go from there. One other thought is that it might be a case=20 sensitivity issue. Do the tables you restored have the same case as the original/production names?=20 > -----Original Message----- > From: Bryce Nesbitt [mailto:bryce1@obviously.com]=20 > Sent: Thursday, February 16, 2006 1:15 PM > To: Apache Torque Users List > Subject: Re: What are possible causes of: IDBroker ... does=20 > not support transactions. >=20 >=20 > Greg Monroe wrote: > > log4j statements in the Torque.properties have never > > worked for me.. try creating a separate log4j.properties > > file in the class path. It generates tons of output > > for me under Tomcat. > > =20 > Got it. But it is the exact same, less than detailed, error message: >=20 >=20 >=20 > DEBUG tcpConnection-6809-0 org.apache.commons.beanutils.BeanUtils - =20 > setProperty(com.myclient.xxx.v2.web.member.LoginForm@dc67e,=20 > userid, [5403]) DEBUG tcpConnection-6809-0=20 > org.apache.commons.beanutils.ConvertUtils - Convert string=20 > '5403' to class 'java.lang.String' DEBUG tcpConnection-6809-0=20 > org.apache.commons.beanutils.ConvertUtils - =20 > Using converter=20 > org.apache.commons.beanutils.converters.StringConverter@14384c2 > DEBUG tcpConnection-6809-0 org.apache.commons.beanutils.BeanUtils - =20 > setProperty(com.myclient.xxx.v2.web.member.LoginForm@dc67e,=20 > pin, [XXXX]) DEBUG tcpConnection-6809-0=20 > org.apache.commons.beanutils.ConvertUtils - Convert string=20 > 'XXXX' to class 'java.lang.String' DEBUG tcpConnection-6809-0=20 > org.apache.commons.beanutils.ConvertUtils - =20 > Using converter=20 > org.apache.commons.beanutils.converters.StringConverter@14384c2 > DEBUG tcpConnection-6809-0=20 > org.apache.struts.action.RequestProcessor -=20 > Validating input form properties > DEBUG tcpConnection-6809-0=20 > org.apache.struts.action.RequestProcessor - =20 > No errors detected, accepting input > DEBUG tcpConnection-6809-0=20 > org.apache.struts.action.RequestProcessor -=20 > Looking for Action instance for class=20 > com.myclient.xxx.v2.web.member.LoginAction > DEBUG tcpConnection-6809-0=20 > org.apache.struts.action.RequestProcessor - =20 > Creating new Action instance > DEBUG Thread-0 org.apache.torque.oid.IDBroker - IDBroker=20 > thread was started. WARN tcpConnection-6809-0=20 > org.apache.torque.oid.IDBroker - IDBroker is being used with=20 > db 'default', which does not support transactions.=20 > IDBroker attempts to use transactions to limit the=20 > possibility of duplicate key generation. Without=20 > transactions, duplicate key generation is possible if=20 > multiple JVMs are used or other means are used to write to=20 > the database. DEBUG tcpConnection-6809-0=20 > org.apache.struts.util.PropertyMessageResources - > getMessage(en_US,unhandledException) >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org > For additional commands, e-mail: torque-user-help@db.apache.org >=20 >=20 Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are = confidential communication or may otherwise be privileged or = confidential and are intended solely for the individual or entity to = whom they are addressed. If you are not the intended recipient you may = not rely on the contents of this email or any attachments, and we ask = that you please not read, copy or retransmit this communication, but = reply to the sender and destroy the email, its contents, and all copies = thereof immediately. Any unauthorized dissemination, distribution or = copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org