Thanks Dag for the fix and porting to 10.3. Hope fully we will have 10.3.1.4RC soon with this fix
Regards Manjula On 7/25/07, Dag H. Wanvik (JIRA) <[EMAIL PROTECTED]> wrote:
[ https://issues.apache.org/jira/browse/DERBY-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515385] Dag H. Wanvik commented on DERBY-2963: -------------------------------------- Committed on the 10.3 branch as svn 559555. > 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, 10.4.0.0 > > Attachments: DERBY-2963-1.diff, 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.
-- Thanks, Manjula.
