[ https://issues.apache.org/jira/browse/DERBY-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304990#comment-17304990 ]
Richard N. Hillegas commented on DERBY-7107: -------------------------------------------- Thanks, Holger. I'm not competent to evaluate the implications of this patch. > NetworkServerControl fails to connect to server started on INADDR_ANY > --------------------------------------------------------------------- > > Key: DERBY-7107 > URL: https://issues.apache.org/jira/browse/DERBY-7107 > Project: Derby > Issue Type: Bug > Components: Network Server > Affects Versions: 10.14.2.0, 10.15.2.0 > Reporter: Holger Rehn > Priority: Critical > Attachments: DERBY-7107.diff > > > If starting a NetworkServerControl on INADDR_ANY (0.0.0.0) it also uses this > address when connecting to the running server instance (e.g. in method > ping(), ...). > Strictly speaking, INADDR_ANY isn't a valid target address. However, under > normal circumstances, this works anyway. But if you have any "security" > software in place that blocks such connections (Firewall or VPN, e.g. Cisco > AnyConnect), you end up with an IOException: > {code}Could not connect to Derby Network Server on host 0.0.0.0, port 1527: > Permission denied: connect.{code} > One simple fix would be to explicitly check the host address 'hostAddress' in > NetworkServerControlImpl.setUpSocket() and if this is INADDR_ANY, use > 'localhost' instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)