Skip site navigation (1) Skip section navigation (2)

Unknown Response Type [some random character]

From: "Geoffrey Ritchey" <ritcheyg(at)mail(dot)wbu(dot)edu>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Unknown Response Type [some random character]
Date: 2002-04-16 22:47:37
Message-ID: NFBBJNOLPACPPLLMBDPKAEMAEMAB.ritcheyg@mail.wbu.edu (view raw or flat)
Thread:
Lists: pgsql-bugs
Your name               :Kexin Wang
Your email address      :wangkx(at)wbu(dot)edu

Your name               :Geoffrey Ritchey
Your email address      :ritcheyg(at)wbu(dot)edu

System Configuration
---------------------
  Architecture (example: Intel Pentium)         :Intel Pentium
  Operating System (example: Linux 2.0.26 ELF)  :Linux Mandrake 8.0
  PostgreSQL version (example: PostgreSQL-7.1.3):PostgreSQL-7.1.3
  Compiler used (example:  gcc 2.95.2)          :gcc 2.96


Please enter a FULL description of your problem:
------------------------------------------------

When running the following query I get the following stack trace.  The
problem seems to only happen after running for hours and sometimes a couple
days.  The query is usually executed every 2 minutes or so.  The actual
value of the 'response type' seems to be relatively random.

It is running from a tomcat jsp/servlet using the jdbc driver.


Execute: select id, reverse_name, ssn, address1, address2, address3,
street1, street2, city, state
, zip1, zip2, phone, work_phone, fax, email from nap where id = -1;
Unknown Response Type ^H
Unknown Response Type ^H
        at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:117)
        at org.postgresql.Connection.ExecSQL(Connection.java:398)
        at org.postgresql.jdbc2.Statement.execute(Statement.java:130)
        at org.postgresql.jdbc2.Statement.executeQuery(Statement.java:54)


Please describe a way to repeat the problem.   Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
The problem seems to happen randomly.  We can't reproduce it at will.  We
are using connection pooling.  Perhaps a problem with more than one thread
using the same connection???




If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------




pgsql-bugs by date

Next:From: Tom LaneDate: 2002-04-16 23:19:30
Subject: Re: [HACKERS] Foreign Key woes -- 7.2 and ~7.3
Previous:From: Bruce MomjianDate: 2002-04-16 19:27:08
Subject: Re: Case sensitivity in psql/pg_dump

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group