[
https://issues.apache.org/jira/browse/DERBY-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302569#comment-17302569
]
Bryan Pendleton commented on DERBY-7107:
----------------------------------------
Oh, I see, I misunderstood. You're not suggesting that it should be wrong to
start the Network Server on 0.0.0.0; you're suggesting that the ping command
should be smart enough to know to avoid trying to connect to 0.0.0.0.
It's an interesting idea. We've certainly had lots of problems with the
loopback ping before. I think the ping command is really designed to test a
client-to-server connection, not to have the server looping back to itself.
See Derby-6853 for an example of a similar suggestion.
I guess I'd see this Jira as more of an enhancement request than a bug report,
though?
> 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
>
> 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)
