[Dspace-tech] PSQL Error when making a copy of postgres db

2009-11-11 Thread Timo Aalto
Hi,

I'm trying to copy a DSpace PostgreSql database from one server to another
to create a separate testing/dev environment. Dumping (pg_dump database 
db.sql) and reloading (psql database db.sql) the SQL to the second server
seems to work fine. However when I try to access the DSpace XMLUI using the
db copy I get the following error:

org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block

I have logging set on debug and the offending(?) SQL query says:

2009-11-11 12:27:51,635 DEBUG org.dspace.storage.rdbms.DatabaseManager @
Running query SELECT * FROM community WHERE NOT community_id IN (SELECT
child_comm_id FROM community2community) ORDER BY name with parameters:

Both servers are RHEL5 with psql (PostgreSQL) 8.1.18. DSpace is version
1.5.2 with the delegated admins patch applied. Vacuuming and reindexing does
not seem to help.

Anyone have ideas on how to fix this?

T

-- 
-- 
Timo Aalto
Planning Officer
University of Helsinki Library
timo dot j dot aalto at helsinki dot fi
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


[Dspace-tech] PSQL error

2007-11-05 Thread Mika Stenberg

I started having these out of nowhere when trying to submit files to 
DSpace. Any ideas how can I fix this. Restaring, re-indexing or 
vacuuming the db doesnt help. My guess is that some item is maliciously 
left hanging and thus blocking the way for other items.

-Mika





org.postgresql.util.PSQLException: ERROR: current transaction is 
aborted, commands ignored until end of transaction block
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1525)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1309)
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354)
at 
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:308)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
at 
org.dspace.storage.rdbms.DatabaseManager.execute(DatabaseManager.java:1492)
at 
org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManager.java:853)
at org.dspace.content.Item.update(Item.java:1420)
at org.dspace.content.Item.create(Item.java:247)
at org.dspace.content.WorkspaceItem.create(WorkspaceItem.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:230)
at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:1134)
at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)
at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)
at 
org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)
at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1591)
at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:852)
at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:123)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:107)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:116)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:192)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:265)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:110)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:102)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)

[Dspace-tech] Psql error

2007-09-05 Thread Mika Stenberg
Im getting a whole lot of errors in my log file (Dspace 1.4.2, Manakin 
1.1 (trunk)) . The one Im worried about is this. Has anyone experienced 
this and perhaps solved it?

Thanks,
Mika


LOG:  unexpected EOF on client connection
org.postgresql.util.PSQLException: An I/O error occured while sending to 
the backend.
 at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:214)
 at 
org.postgresql.jdbc2.AbstractJdbc2Connection.executeTransactionCommand(AbstractJdbc2Connection.java:617)
 at 
org.postgresql.jdbc2.AbstractJdbc2Connection.rollback(AbstractJdbc2Connection.java:654)
 at 
org.apache.commons.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:265)
 at 
org.apache.commons.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:265)
 at 
org.apache.commons.dbcp.PoolingDriver$PoolGuardConnectionWrapper.rollback(PoolingDriver.java:348)
 at org.dspace.core.Context.abort(Context.java:251)
 at org.dspace.core.Context.finalize(Context.java:384)
 at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
 at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
 at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
 at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
Caused by: java.net.SocketException: Socket closed
 at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
 at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
 at 
java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
 at org.postgresql.core.PGStream.flush(PGStream.java:532)
 at 
org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:672)
 at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:187)
 ... 11 more
java.sql.SQLException: Already closed.
 at 
org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:77)
 at 
org.apache.commons.dbcp.PoolingDriver$PoolGuardConnectionWrapper.close(PoolingDriver.java:240)
 at 
org.dspace.storage.rdbms.DatabaseManager.freeConnection(DatabaseManager.java:733)
 at org.dspace.core.Context.abort(Context.java:260)
 at org.dspace.core.Context.finalize(Context.java:384)
 at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
 at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
 at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
 at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
LOG:  unexpected EOF on client connection

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Psql error

2007-09-05 Thread James Rutherford
On Wed, Sep 05, 2007 at 04:27:27PM +0300, Mika Stenberg wrote:
 LOG:  unexpected EOF on client connection

This is a problem caused by DSpace not properly closing database
connections. It's nothing to worry about really (although it is probably
indicative of sloppy / incorrect use of the Context somewhere); all that
has happened is that the postgres JDBC driver is trying to use a
connection that it assumes is open when it's not. When the driver
realised it's actually closed, it will just go hunting for another. I
think this is in the list of things that need cleaning up in the near
future...

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: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now   http://get.splunk.com/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech