Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 59578 invoked from network); 8 Jul 2005 08:17:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Jul 2005 08:17:14 -0000 Received: (qmail 6548 invoked by uid 500); 8 Jul 2005 08:17:08 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 6489 invoked by uid 500); 8 Jul 2005 08:17:07 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 6469 invoked by uid 99); 8 Jul 2005 08:17:07 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2005 01:16:56 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id BB14B16; Fri, 8 Jul 2005 10:16:53 +0200 (CEST) From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 35338] - [net] FTPClient.listFiles() hangs on Red Hat Linux X-Bugzilla-Reason: AssignedTo Message-Id: <20050708081653.BB14B16@ajax.apache.org> Date: Fri, 8 Jul 2005 10:16:53 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35338 dfs@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From dfs@apache.org 2005-07-08 10:16 ------- I couldn't reproduce the issue on internal IPv6 systems nor by accessing the external host ftp.unicamp.br mentioned in one of the comments. The PORT command from the trace looks fine. I think we can rule out IPv6 issues. It's almost definitely a local configuration issue. The thing to do would be to capture a trace of the FTP protocol traffic (just the FTP commands going back and forth) for the native ftp command (which apparently works) and for the failed FTPClient and compare the two (have both of them perform exactly the same transaction). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org