[
https://issues.apache.org/jira/browse/DERBY-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515126
]
Manjula Kutty commented on DERBY-2963:
--------------------------------------
This patch works fine. I tested the following scenarios
1. starting the server by giving -h option with ipaddress
java org.apache.derby.drda.NetworkServerControl start -h 9.72.143.153
2. Starting the server with -h 0.0.0.0
java org.apache.derby.drda.NetworkServerControl start -h 0.0.0.0
3. starting the server by giving -h option with ipaddress on ipv6 machines
java org.apache.derby.drda.NetworkServerControl start -h
2002:92a:8f7a:13:9:42:74:19
All of them works fine. I would appreciate if we could include this patch in
our release candidate
> 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: 10.3.1.2, 10.3.1.3
> Environment: SuseLinux 10
> IBM JVM 1.5
> Reporter: Daniel John Debrunner
> Assignee: Dag H. Wanvik
> Priority: Blocker
> Fix For: 10.3.1.4
>
> Attachments: DERBY-2963-1.diff, DERBY-2963-1.stat
>
>
> 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 10.2.2.0.
> 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.
