Okay, using this blanket statement:
grant {
permission java.net.SocketPermission "localhost", "resolve";
permission java.net.SocketPermission "127.0.0.1:3306",
"connect,resolve";
};
The webapp works when tomcat is started normally. This is acceptable
while the machine is being used
I haven't gotten it working yet, but I think David may be on the right
track. Here's what I did:
I changed my file at '/etc/tomcat5/policy.d/03catalina.policy' to
properly point to my connector.jar and also changed the permissions to
include:
permission java.net.SocketPermission "localhost", "con
java.security.AccessControlException indicates you are running tomcat
with the security manager. You'll need to edit your catalina.policy
file to allow this connection. The policy file itself has a number of
examples, here's just one modified to your situation below:
grant codebase
"jar:fil
Cameron,
> For some reason tomcat can't connect to the database
> and create a
> connection pool, even though a normal client can
> connect just fine. I
> even wrote a small java program to connect using
> JDBC, in case that
> was the problem. I used the same parameters given to
> tomcat and again
Cameron,
> I've tried using the IP address instead, unfortunately that didn't work.
:(
> The entry in the hosts file is defined as you said.
:( :(
> For some reason tomcat can't connect to the database and create a
> connection pool, even though a normal client can connect just fine. I
> even wr
Thanks for the quick replies.
Martin:
No luck with your advice. I'm not sure there's a problem with mysql
permissions, as I can log in with a mysql client from the local
machine and access the database as normal. The original command used
to set the permissions was 'GRANT ALL ON DB.* TO 'User'@'%
Cameron,
You wrote:
> I have a newly installed and configured Ubuntu
> server running
> Tomcat5.5 and Mysql 5.0. This server was created in
> an attempt to
> migrate from a Red Hat server in a similar
> configuration, running the
> exact same webapp. Most of the
> configuration/classpath differen
Cameron,
> When our webapp trys to connect to the database on localhost, an exception
>
> 'java.security.AccessControlException: access denied
> (java.net.SocketPermission localhost resolve)'
In the past, the Connector/J JDBC client would often use
"localhost.localdomain" as the hostname, even t
or email and destroy the original
message without making a copy. Thank you.
- Original Message -
From: "Cameron Currie" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, July 19, 2006 2:23 PM
Subject: Database Connection Error Cannot create PoolableConnectionFactory
> Hello ev
pplets and attempts to connect to different hosts.
This case involves a webapp, connecting to localhost, using a
configuration that is known to work. I am simply baffled.
The following stacktrace is generated:
javax.servlet.ServletException: Database Connection Error
Cannot create PoolableConnect
10 matches
Mail list logo
