On Tue, Mar 04, 2008 at 08:40:32AM +0000, Charlotte Pollock wrote: > I'm getting an the following intermittent error > > database_error:org.postgresql.util.PSQLException: ERROR: current transaction > is aborted, commands ignored until end of transaction block > > With no clear pattern as to why > > What I really would like to do is to see the raw SQL that is causing > postgres to error > > Does anyone know of a way to debug this error?
The only way to do this is to change your logging level from INFO to DEBUG in your log4j.properties (you'll need to redeploy DSpace after making the change, of course). Once you've done that, your dspace.log should contain all the queries sent to the db. cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL". ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
