|
Re: [CDO] Repository recovery fails after crash with stanalone CDO sever with postgresql [message #931663 is a reply to message #931515] |
Wed, 03 October 2012 12:02 |
|
Hi Yvan,
Vik, who's developed the PostgresAdapter is absent for a while. I have no Postgres experience at all. Google shows this
kind of issue with many higher-level frameworks:
https://www.google.de/search?hl=de&site=&source=hp&q=org.postgresql.util.PSQLException%3A+ERROR%3A+current+transaction+is+aborted%2C+commands+ignored+until+end+of+transaction+block+&oq=org.postgresql.util.PSQLException%3A+ERROR%3A+current+transaction+is+aborted%2C+commands+ignored+until+end+of+transaction+block+&gs_l=hp.3...6478.6478.0.6667.1.1.0.0.0.0.0.0..0.0...0.0...1c.1.PYZHuUUWZYM
Can it be that this is not the first error in the log? What about possible "|OutOfMemoryError: PermGen space" or
similar, so that your exception is kind of a follow-up problem?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
Am 03.10.2012 11:25, schrieb Yvan Lussaud:
> Hi,
>
> for some reason I have a standalone CDO server that crashed. So I restarted it and now I get the following error :
>
> Exception in thread "main" org.eclipse.net4j.db.DBException: org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
> at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.ObjectTypeTable.getMaxID(ObjectTypeTable.java:185)
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.DelegatingObjectTypeMapper.getMaxID(DelegatingObjectTypeMapper.java:85)
> at
> org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.AbstractHorizontalMappingStrategy.repairAfterCrash(AbstractHorizontalMappingStrategy.java:94)
> at org.eclipse.emf.cdo.server.internal.db.DBStore.repairAfterCrash(DBStore.java:679)
> at org.eclipse.emf.cdo.server.internal.db.DBStore.reStart(DBStore.java:661)
> at org.eclipse.emf.cdo.server.internal.db.DBStore.doActivate(DBStore.java:556)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:76)
> at org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(LifecycleUtil.java:114)
> at org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(LifecycleUtil.java:104)
> at org.eclipse.emf.cdo.internal.server.Repository.doActivate(Repository.java:1845)
> at org.eclipse.net4j.util.lifecycle.Lifecycle.activate(Lifecycle.java:76)
> at org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(LifecycleUtil.java:114)
> at org.eclipse.net4j.util.lifecycle.LifecycleUtil.activate(LifecycleUtil.java:104)
> at org.eclipse.emf.cdo.server.CDOServerUtil.addRepository(CDOServerUtil.java:208)
> at ch.paranor.reverse.specification.server.CDOServer.start(CDOServer.java:230)
> at ch.paranor.reverse.specification.server.CDOServer.main(CDOServer.java:275)
> Caused by: 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:2062)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:252)
> at org.eclipse.emf.cdo.server.internal.db.mapping.horizontal.ObjectTypeTable.getMaxID(ObjectTypeTable.java:174)
> ... 15 more
>
>
> It happen when running the following SQL statement :
>
> SELECT MAX(cdo_id) FROM cdo_objects;
>
>
> So I tried to run in from the psql util :
>
>
> SELECT MAX(cdo_id) FROM cdo_objects;
> max -----
> 73
> (1 row)
>
>
> It works fine... so I thought it was the JDBC driver version that was not up to date. My 8.44 server is 9.1. I was
> using the JDBC driver v3 for postgresql 8.4. I moved to JDBC driver v3 for postgresql 9.1. But I still have the same
> issue.
>
>
> Any idea of how I can recover this repository ?
>
> regards,
> Yvan.
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04473 seconds