From: | Guido Fiala <guido(dot)fiala(at)dka-gmbh(dot)de> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Query was cancelled - reason? |
Date: | 2004-07-02 07:11:13 |
Message-ID: | 200407020911.13470.guido.fiala@dka-gmbh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Am Donnerstag, 1. Juli 2004 13:20 schrieb Oliver Jowett:
> Guido Fiala wrote:
> > Hello,
> >
> > i'am currently run into a strange problem with fast subsequent updates in
> > the same table.
> >
> > The application is quite complex, so its difficult to to sent a code
> > snippet, i included the network traffic instead:
> >
> > This is whats happening:
>
> [... COMMIT gets cancelled ...]
>
> > So why comes the commit-error?
>
> Three possibilities I can think of:
>
> - Something is sending SIGINT to the backend process.
> - You are calling JDBC's Statement.cancel() method (see below) which
Thank you so much - you are right ! This it was. I didn't destroy my thread
that was intentend to cancel the query, so it run on and triggered...
...
AFAIK the Statement.setqueryTimeOut() is currently not implemented/used
or has this already changed in recent driver snapshots?
> ends up sending a SIGINT (indirectly via a backend process).
Why can't i see the SIGINT in network traffic?
Guido
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-07-02 10:24:54 | Re: Issue with now() within a transaction in pg74.213.jdbc.jar |
Previous Message | John Pagakis | 2004-07-02 06:17:04 | Re: Issue with now() within a transaction in pg74.213.jdbc.jar |