I don't think this is an operating system issue or a network issue. The message is something to do with
Java security, it's coming from the Java security manager that's configured into your
Tomcat instance.
I had the same thing in Websphere when I tried to use RMI (not JDBC, but it was the same complaint, connecting to a socket). I solved that one by configuring it to turn on (not off, on!) Java 2 security and providing a security policy file. But other people don't seem to have a problem in using JDBC in Tomcat so surely there's a simpler way to fix your configuration. I haven't used Tomcat so I couldn't guess how to do it.