RE: JDBC for 7.0 - Tuple received before MetaData ex ception

From: Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
To: "'Gunnar R|nning'" <gunnar(at)candleweb(dot)no>, pgsql-interfaces(at)postgresql(dot)org
Subject: RE: JDBC for 7.0 - Tuple received before MetaData ex ception
Date: 2000-05-26 06:29:47
Message-ID: 1B3D5E532D18D311861A00600865478CF1AE5E@exchange1.nt.maidstone.gov.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Not sure, but the only way this could happen is what it states: It's
getting tuples before it's expecting to get them.

Are you running multiple threads on the same connection?

Anyhow, the query looks innocent.

Peter

--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.

-----Original Message-----
From: Gunnar R|nning [mailto:gunnar(at)candleweb(dot)no]
Sent: Thursday, May 25, 2000 1:35 PM
To: pgsql-interfaces(at)postgresql(dot)org
Subject: [INTERFACES] JDBC for 7.0 - Tuple received before MetaData
exception

Hello,

I'm currently going over my log files to search for suspect error
messages. I found one suspicous error message(I only have one instance
of
this exception in my log files). Does anybody know what the reason for
this
error could be ? e.g. something on the database server side, concurrency
problems etc.

Regards,

Gunnar

[abJDBCServer] doQuery(LocationDS) "SELECT LOC_ID , LOC_TYPE , LOC_NAME
, LOC_PARENT FROM LOCATION WHERE LOC_PARENT IS NULL AND NOT LOC_TYPE=0
ORDER BY LOC_NAME"
abJDBCServer: handle open link exception = Tuple received before
MetaData.
Tuple received before MetaData.
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(Compiled Code)
at
org.postgresql.util.PSQLException.<init>(PSQLException.java:22)
at org.postgresql.Connection.ExecSQL(Compiled Code)
at org.postgresql.jdbc2.Statement.execute(Compiled Code)
at org.postgresql.jdbc2.Statement.executeQuery(Compiled Code)
at
progress.apptivity.agent.server.abJDBCServer.doQueryImpl(Compiled Code)
at
progress.apptivity.agent.server.abJDBCServer.doQueryImpl(Compiled Code)
at progress.apptivity.agent.server.abJDBCServer.doQuery(Compiled
Code)
at
progress.apptivity.agent.server.abJDBCServer.serverRequest(Compiled
Code)
at SearchFasterServerEvents.serverRequest(Compiled Code)
at progress.apptivity.server.abServer.serverRequest(Compiled
Code)
at
progress.apptivity.server.abQuerySetImpl.serverRequest(Compiled Code)
at
progress.apptivity.client.iiop._abQuerySetImplBase.invoke(Compiled Code)
at IE.Iona.OrbixWeb.CORBA.ServerDispatcher.dispatch(Compiled
Code)
at
IE.Iona.OrbixWeb.CORBA.ServerDispatcher.system_dispatch(Compiled Code)
at
IE.Iona.OrbixWeb.CORBA.BOAImpl.continueThreadDispatch(Compiled Code)
at IE.Iona.OrbixWeb.CORBA.ORB.continueThreadDispatch(Compiled
Code)
at progress.apptivity.server.iiop.ow.a25.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Peter Mount 2000-05-26 08:08:28 RE: Postgresql 7.0 JDBC exceptions - broken connecti ons ?
Previous Message Michael Meskes 2000-05-26 06:18:56 Re: importing from other dbases