Re: JDBC driver works in ccommand line, not in Tomcat5

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Chris Baty <batymohn(at)yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: JDBC driver works in ccommand line, not in Tomcat5
Date: 2007-09-05 15:07:24
Message-ID: 13178.1189004844@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Kris Jurka <books(at)ejurka(dot)com> writes:
> Turns out this is pretty easy to do, I'm just not sure what the best text
> to report to the user is, so far I have:

> Your security policy has prevented the connection from being
> attempted. You must grant the connect java.net.SocketPermission
> to the database server host and port that you wish to connect to.

Can you really tell for sure that it's security policy and not something
else? A message as specific as this would be downright
counterproductive if it's wrong.

FWIW, the backend's style guide would suggest dividing that into an
ERROR and a HINT, particularly if the HINT could be mistaken.

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Josh Berkus 2007-09-05 15:25:26 Caching driver on pgFoundry?
Previous Message Heikki Linnakangas 2007-09-05 14:07:11 Re: PreparedStatement rounds doubles to scale 14 during update