[ 
https://issues.apache.org/jira/browse/FTPSERVER-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640897#action_12640897
 ] 

David Latorre commented on FTPSERVER-136:
-----------------------------------------

Actually this behaviour I mentioned was changed in Java SE 6 (when there is no 
Security Manager) but my explanation to the problem was incorrect (although the 
problem I pointed out would also affect if we fixed this).

Now, this is correct (I think)
We are building the InetAddress object representing the External Ip Address 
(when explicitly stated) inside the  ListenerBeanDefinitionParser so,  as 
Amichal said, the IP address is never looked up again (InetAddress will lookup 
the hostname if we didn't provide one when we created the object but won't even 
know that we didn't provide a numeric ip address so it won't look it up again).

The easiest solution I can see is to store the address information in a String 
fiend and have a  getter which will return an InetAddress or retrieve it as a 
String and build the object when appropriate (Not a problem since we also need 
to retrieve the local ip if we didn't configure the field in the xml).

 
  



> incorrent IP used in opening data channel
> -----------------------------------------
>
>                 Key: FTPSERVER-136
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-136
>             Project: FtpServer
>          Issue Type: Bug
>         Environment: Windows XP
>            Reporter: Amichai Rothman
>            Assignee: Niklas Gustavsson
>            Priority: Minor
>             Fix For: 1.0-M4
>
>
> The IP used in opening the data channel (DATA command) appears to be 
> determined when the ftp server starts, and never updated again. On systems 
> where the IP address might change (such as any dynamic dns host) this causes 
> all data connections to fail, and requires a full restart of the service 
> whenever the IP address changes (which makes the availability of the ftp 
> server unreliable for practical use).

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

Reply via email to