The error you're seeing comes from before. You only see the fact that
there was an error, and postgres is ignoring your queries until you roll
back. I bet you have a glitch in your transaction handling code, like
opening a transaction, getting an error on it, hibernate throws an error
and you don't have a finally clause to roll back the transaction.

HTH,
Csaba.


On Tue, 2006-01-31 at 08:13, Myatluk Andrey wrote:
> Hi!
> 
> I have an application, consisting of Struts 1.2 + Tomcat 5.5 + Hibernate
> 3.1 + PostgreSQL 8.1
> 
> The application is developed on WinXP and installed on Fedora Core 4.
> 
> On local machine everything works OK. Both databases are created from
> the same script and application is the same.
> 
> But when installed on FC, I get the following exception:
> 
> Hibernate: select nextval ('hibernate_sequence') Jan 30, 2006 8:21:35 PM
> org.hibernate.util.JDBCExceptionReporter logExceptions
> WARNING: SQL Error: 0, SQLState: 25P02
> Jan 30, 2006 8:21:35 PM org.hibernate.util.JDBCExceptionReporter
> logExceptions
> SEVERE: ERROR: current transaction is aborted, commands ignored until
> end of transaction block Jan 30, 2006 8:21:35 PM
> 
> Although when I'm trying to call hibernate sequence it works fine.
> 
> twix=#  select nextval ('public.hibernate_sequence');  nextval
> ---------
>        3
> (1 row)
> 
> twix=#  select nextval ('hibernate_sequence');  nextval
> ---------
>        4
> (1 row)
> 
> The sequence was created with the following command:
> twix=# create sequence hibernate_sequence; CREATE SEQUENCE
> 
> I don't see what the problem could be.
> 
> Because of the connectivity problem could not connect to remote database
> with pgAdmin. But it's the question for the next post.
> 
> Andrey
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to