| Lists: | pgsql-general |
|---|
| From: | "Marcelo de Moraes Serpa" <celoserpa(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | "Protocol error. Session setup failed" (PostgreSQL 8.3devel/postgresql-8.3dev-600.jdbc3) |
| Date: | 2007-04-28 13:34:54 |
| Message-ID: | 1e5bcefd0704280634p33cd6e67g9ca6357e334abb0d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
Hello,
I've built PostgreSQL 8.3 devel with VC++ 2005, done all the db
initialization process (creating the data dir using initdb, registering it
as a service using pg_ctl, etc) and tested by connecting to it through
pgAdmin III, I even built a C extension and ran it as a SP in the pgAdmin
SQL console.
I then restored a backup with the database of my under-development java
application in the hope that it would connect to this db transparently (I
have of course changed the jdbc driver to match the 8.3devel version).
When I tried to run my web java application, I received the following
PSQLException: ""Protocol error. Session setup failed"
What could be happening?
Note: I've attached the tomcat stack trace to the error.
Thanks,
Marcelo.
| Attachment | Content-Type | Size |
|---|---|---|
| stacktrace.txt | text/plain | 6.0 KB |
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Marcelo de Moraes Serpa <celoserpa(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: "Protocol error. Session setup failed" (PostgreSQL 8.3devel/postgresql-8.3dev-600.jdbc3) |
| Date: | 2007-04-28 21:01:34 |
| Message-ID: | Pine.BSO.4.64.0704281659240.13499@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
On Sat, 28 Apr 2007, Marcelo de Moraes Serpa wrote:
> I've built PostgreSQL 8.3 devel with VC++ 2005, done all the db
>
> When I tried to run my web java application, I received the following
> PSQLException: ""Protocol error. Session setup failed"
>
This is a known bug in the server in CVS. A recent patch broke the
ability for clients to set the encoding they wish to converse in.
Kris Jurka