Обсуждение: JDBC driver works in ccommand line, not in Tomcat5

Il giorno mar, 04/09/2007 alle 07.11 -0700, Chris Baty ha scritto:
> Hi Guys,
> I'm trying to get Tomcat 5 to  access psql.  I created a "test'
> database and put several drivers in common/lib.  I keep getting
>
> org.postgresql.util.PSQLException: Something unusual has occured to
> cause the driver to fail. Please report this exception.
[...]

Could you please post the complete exception trace?

On Tue, 4 Sep 2007, Chris Baty wrote:

> I'm trying to get Tomcat 5 to access psql.  I created a "test' database
> and put several drivers in common/lib.  I keep getting
>
> org.postgresql.util.PSQLException: Something unusual has occured to
> cause the driver to fail. Please report this exception.

This is probably caused by a permission denied error because you are
running tomcat with a security policy that does not let you connect to
outside resources (such as a database).

We should probably do a better job of catching and reporting this error
with a helpful suggestion instead of the obscure message and request for a
report above.

Kris Jurka

On Wed, 5 Sep 2007, Kris Jurka wrote:

> This is probably caused by a permission denied error because you are running
> tomcat with a security policy that does not let you connect to outside
> resources (such as a database).
>
> We should probably do a better job of catching and reporting this error with
> a helpful suggestion instead of the obscure message and request for a report
> above.
>

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.

It's a little awkward because it tries to tell you what you need to do,
but since there are a number of ways to define a policy for different app
servers and configurations, there's no way to be specific enough to
solve the problem right here.  Anyone have a better suggestions?

Kris Jurka

Kris Jurka <books@ejurka.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

On Wed, 5 Sep 2007, Tom Lane wrote:

> Kris Jurka <books@ejurka.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.

We can be pretty sure by checking if the connection setup failed because
of an AccessControlException:

http://java.sun.com/j2se/1.5.0/docs/api/java/security/AccessControlException.html


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

We don't have separate fields, but I agree it's a little strong, perhaps
"You probably need to" instead of "You must".

Kris Jurka