db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Kutty (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2963) AccessControlException: Access denied java.net.SocketPermission <client ip> accept,resolve
Date Fri, 20 Jul 2007 19:18:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514288

Manjula Kutty commented on DERBY-2963:

I found it happening on both Ipv6 and Ipv4 machines. Ipv6 machines gave me the stack trace
as follows
java.security.AccessControlException: Access denied (java.net.SocketPermission [2002:92a:8f7a:13:9:42:73:218]:32813
        at java.security.AccessController.checkPermission(AccessController.java:104)
        at java.lang.SecurityManager.checkPermission(SecurityManager.java:547)
        at java.lang.SecurityManager.checkAccept(SecurityManager.java:1172)
        at java.net.ServerSocket.implAccept(ServerSocket.java:466)
        at java.net.ServerSocket.accept(ServerSocket.java:433)
        at org.apache.derby.impl.drda.ClientThread$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(AccessController.java:242)
        at org.apache.derby.impl.drda.ClientThread.run(Unknown Source)

Ipv4 machine didn't give any exception other the the following error message
ij>connect 'jdbc:derby://incus.rtp.raleigh.ibm.com:1527/ipv6db;create=true;user=user2;password=pass2';
ERROR 58009: Insufficient data while reading from the network - expected a minimum of 6 bytes
and received only -1 bytes.  The connection has been terminated.

> AccessControlException: Access denied java.net.SocketPermission <client ip> accept,resolve
> ------------------------------------------------------------------------------------------
>                 Key: DERBY-2963
>                 URL: https://issues.apache.org/jira/browse/DERBY-2963
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>         Environment: SuseLinux 10
> IBM JVM 1.5
>            Reporter: Daniel John Debrunner
>            Priority: Critical
> I start the server using an ipv4 address
> java derbyrun.jar server start -h x.x.x.x
> Then I connect from a remote client  and hit an AccessControlException
> The ip in the exception is that of the *client*, not the server.
> This setup works in
> Same problem if the hostname is in derby.properties
> Problem can be worked around by using -noSecurityManager when starting the server

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message